On Bering-1.0, using ntpdate, shorewall, dnscache, tinydns. During boot, ntpdate runs right after hwclock, during rc.S, before shorewall, before tinydns, before dnscache: RCDLINKS="S,S51"
/etc/rcS.d/ 22 Jan 21 17:37 S10checkroot.sh -> ../init.d/checkroot.sh 18 Jan 21 17:37 S20modutils -> ../init.d/modutils 21 Jan 21 17:37 S35mountall.sh -> ../init.d/mountall.sh 18 Jan 21 17:37 S39ifupdown -> ../init.d/ifupdown 21 Jan 21 17:37 S40hostname.sh -> ../init.d/hostname.sh 20 Jan 21 17:37 S40networking -> ../init.d/networking 21 Jan 21 17:37 S45mountnfs.sh -> ../init.d/mountnfs.sh 17 Jan 21 17:37 S50hwclock -> ../init.d/hwclock 17 Jan 21 17:37 S51ntpdate -> ../init.d/ntpdate <==== 21 Jan 21 17:37 S55bootmisc.sh -> ../init.d/bootmisc.sh 17 Jan 21 17:37 S55urandom -> ../init.d/urandom This can't work during boot, as my network needs the firewall and nameservice to be completely functional. Am I the only one who thinks ntpdate should run here, not in rcS, but in rc2? RCDLINKS="2,S90" /etc/rc2.d/ 19 Jan 21 17:37 S41shorewall -> ../init.d/shorewall 18 Jan 21 17:37 S45dnscache -> ../init.d/dnscache 17 Jan 21 17:37 S47tinydns -> ../init.d/tinydns 14 Jan 21 17:37 S89cron -> ../init.d/cron 17 Jan 21 17:37 S90ntpdate -> ../init.d/ntpdate <------ 19 Jan 21 17:37 S99rmnologin -> ../init.d/rmnologin Conceptually, should the system be trying to run client services over the network during boot to admin state? I don't think that's in the spirit of init S. Regards, Matthew ------------------------------------------------------- This SF.NET email is sponsored by: SourceForge Enterprise Edition + IBM + LinuxWorld = Something 2 See! http://www.vasoftware.com _______________________________________________ leaf-devel mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/leaf-devel
