-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA256 On 2010-05-18 01:06, Marc Chamberlin wrote:
On 5/16/2010 1:36 PM, Carlos E. R. wrote:
On Sunday, 2010-05-16 at 12:54 -0700, Marc Chamberlin wrote:
On 5/5/2010 1:54 PM, Carlos E. R. wrote:
Carlos - Thanks for your response... I took a bit of time to try an chase down an answer to your questions, so I temporarily reconfigured my system back to using fstab to mount the network drive...
I think you can use the "nofail" option in fstab, so that the mount process will not halt. Or perhaps, "noauto", which makes it not even attempt to mount it. But then, the "nfs" client service script will not attempt to mount it either. My guess is that it might suceed with "nofail". I'm not sure. Or perhaps there is an option to tell the initial mount not to try mount remote filesystems (it is made this early because a system may need to mount /usr remotely).
Neither the "nofail" nor the "noauto" options corrected the delay of getting the second network interface started.
That's not good...
And you are right, network service starts after "local_fs". However, there is a "remote_fs", which I'm not sure which script provides. The idea would be to make sure that the script providing "remote_fs" has as as "Required-Start" full network.
Ah, it is defined in /etc/insserv.conf (man 8 insserv):
# # All remote filesystems are mounted (note in some cases /usr may # be remote. Most applications that care will probably require # both $local_fs and $remote_fs) # $remote_fs $local_fs +nfs +smbfs
So, it is "nfs". And it is in the required start:
# Provides: nfs # Required-Start: $network $portmap
Now, when service "network" succeeds, is your second interface up?
I tried to instrument the network startup script in init.d and discovered a hitch... The network is started up before the syslog daemon, therefore I cannot get it to record what is happening when the script is ran, during boot up... ( I was using the -xv option for bash, embedded echo statements, and an ifconfig at then end of the "start" section) And syslog is defined as being dependent on network... I am afraid I do not know enough about Linux to figure out how to instrument the start up of the network daemon during the early phases of boot up.. so will need some help to accomplish that in order to answer your question...
Mmmm... there are some services that are split in two, one of them named "early" or something similar. I guess syslog starts after network because the logs can be sent over the network to another machine. Indeed, there is a service named "earlysyslog" and another is "syslog". The first does not depend on anything, the second depends on the network. And looking at the code of the "earlysyslog" script, I see that the author is not very sure that it will work! Look: case "$SYSLOG_DAEMON" in syslog-ng) while read line ; do case "$line" in \#*|"") continue ;; *udp\ *|*udp\(*) exit 0 ;; *tcp\ *|*tcp\(*) exit 0 ;; esac done < ${config} ;; *) # in hope this works with the rsyslog.early.conf file # (hard to implement for rsyslog with its includes/if # statements)... while read select action ; do case "$select" in \#*|"") continue ;; esac case "$action" in *@*) exit 0 ;; esac done < ${config} ;; esac and rsyslog is the default in oS 11.2, so... that's your problem precisely, network init problems will not be logged.
Are you sure your eth1 is listed as "MANDATORY"? I think it is here:
/etc/sysconfig/network/config:MANDATORY_DEVICES=""
Yes, both eth0 and eth1 are specified as mandatory....
Well... dunno. You have a solution that works, so you may leave it at that. You could report the problem in Bugzilla, so that devs try to solve it for good sometime. But I can tell you what I would do, every body has his own preferred bag of tricks O:-) I would define the lines in fstab for those external mounts as "noauto,nofail". This means that they will not be automatically mounted, nor will they abort the sequence attempting to fsck a non existing device. I hope. Then I would add a new service that would run "mount /externalwhatever" adjusted to be run late in the start sequence (the "skeleton script is just that). Easier, "/etc/init.d/after.local" should work: #!/bin/bash mount /externalwhatever And, if that hangs or delays, you could try: mount /externalwhatever & so that it runs in the background. - -- Cheers / Saludos, Carlos E. R. (from 11.2 x86_64 "Emerald" GM (Minas Tirith)) -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.12 (GNU/Linux) Comment: Using GnuPG with SUSE - http://enigmail.mozdev.org/ iF4EAREIAAYFAkvyWfQACgkQja8UbcUWM1w85AD/fGcDdcjpXWWbvOq13oQK2dgE MA1k7ChKAoUVQUfvaEYA/2VgdJuv5lEVqAi95Txj5RqESUlZD0gChniFOOz5YSqN =Fvp6 -----END PGP SIGNATURE----- -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org