| View previous topic :: View next topic |
| Author |
Message |
tim99
n00b
Joined: 27 May 2003
Posts: 16
|
 Posted: Sat Sep 03, 2005 8:58 pm Post subject: Baselayout and network is backgrounding |
 |
|
Hi,
I installed the new baselayout 1.12 with expiriencing the following:
On boot I can't see the network device startup anymore. It seems to be, that the net.ethx are started in background. But when the startup scripts reach e.g. the ntp-client or apache, the network dev is not up already, so that their startup fails.
Is it possible to bring the network script back to the foreground?
Regards,
Tim |
|
| Back to top |
|
 |
unixtroll
n00b
Joined: 19 Aug 2003
Posts: 41
|
| Posted: Sat Sep 03, 2005 10:09 pm Post subject: |
|
|
| Perhaps it has something to do with the RC_PARALLEL_STARTUP &RC_NET_STRICT_CHECKING options in /etc/conf.d/rc. |
|
| Back to top |
|
|
tim99
n00b
Joined: 27 May 2003
Posts: 16
|
| Posted: Sun Sep 04, 2005 7:18 am Post subject: |
|
|
This is my /etc/init.d/rc file:
| Code: |
# Set to "yes" if you want the rc system to try and start services
# in parallel for a slight speed improvement.
RC_PARALLEL_STARTUP="no"
# RC_NET_STRICT_CHECKING allows some flexibility with the 'net' service.
# The following values are allowed:
# none - The 'net' service is always considered up.
# no - This basically means that at least one net.* service besides net.lo
# must be up. This can be used by notebook users that have a wifi and
# a static nic, and only wants one up at any given time to have the
# 'net' service seen as up.
# lo - This is the same as the 'no' option, but net.lo is also counted.
# This should be useful to people that do not care about any specific
# interface being up at boot.
# yes - For this ALL network interfaces MUST be up for the 'net' service to
# be considered up.
RC_NET_STRICT_CHECKING="lo"
|
Setting RC_STRICT_SETTING to "no" results in that e.g. the apache start script doesn't start because the "net" service has not started yet.
Setting it to "lo" effects, that the startup script starts, because the "net" service is up, but starting e.g. the ntp-client fails, because the network interface (not the "net" script) is not up yet. |
|
| Back to top |
|
|
UberLord
Retired Dev
Joined: 18 Sep 2003
Posts: 6835
Location: Blighty
|
|
| Back to top |
|
|
tim99
n00b
Joined: 27 May 2003
Posts: 16
|
| Posted: Wed Sep 07, 2005 7:10 pm Post subject: |
|
|
Hi,
my runlevels seem to be OK:
| Code: | >rc-status -a
Runlevel: boot
keymaps [ started ]
clock [ started ]
localmount [ started ]
consolefont [ started ]
modules [ started ]
hostname [ started ]
net.lo [ started ]
serial [ started ]
urandom [ started ]
checkroot [ started ]
rmnologin [ started ]
bootmisc [ started ]
checkfs [ started ]
Runlevel: default
xdm [ started ]
ntp-client [ stopped ]
acpid [ started ]
cupsd [ started ]
local [ started ]
svnserve [ started ]
domainname [ started ]
metalog [ started ]
coldplug [ started ]
net.ath0 [ started ]
pcmcia [ started ]
netmount [ started ]
cpufreqd [ started ]
apache2 [ stopped ]
postgresql [ started ]
bluetooth [ started ]
portmap [ started ]
alsasound [ started ] |
When I normaly boot, there are no message, saying that my net.ath0 went up. With the old baselayout, I got messages like | Code: |
* Starting ath0
* Starting wpa_supplicant on ath0 ...
ioctl[SIOCSIWPMKSA]: Operation not supported [ ok ]
* Starting wpa_cli on ath0 ... [ ok ]
* ath0 connected to "network" at 00:FF:FF:FF:FF:FF
* ath0 configured with address 192.168.1.100/24
|
|
|
| Back to top |
|
|
UberLord
Retired Dev
Joined: 18 Sep 2003
Posts: 6835
Location: Blighty
|
|
| Back to top |
|
|
tim99
n00b
Joined: 27 May 2003
Posts: 16
|
| Posted: Sat Sep 10, 2005 1:15 pm Post subject: |
|
|
Is is possible to prevent net.ath from being started by hotplug/coldplug?
Regards
Tim |
|
| Back to top |
|
|
UberLord
Retired Dev
Joined: 18 Sep 2003
Posts: 6835
Location: Blighty
|
|
| Back to top |
|
|
|
Networking & Security
