Marieke Thayer wrote:
> I fixed the parameters in Redboot to get my network up. I no longer see
> totally wrong ip_addresses going by in the boot process now too. eth0
> now comes up when I boot. Yeah!
>
> After I did that I looked at the ntpdate files, especially the one in
> /etc/init.d . It runs differently than if you just type "ntpdate -u
> ip_address". "/etc/init.d/ntpdate start|restart" seem to work quite
> nicely. Just before I read this, I found that in /etc/rcS.d I have
> pointers to hwclockfirst.sh and hwclock.sh but no pointer to ntpdate .
> So my system is set up to get its date from the non-existent hardware
> clock. Now I have to figure out what number to give ntpdate and find the
> courage to actually modify my init process. Should it be S18 like
> hwclockfirst.sh or S50 like hwclock.sh . Probably the latter because,
> networking is S40.
>
> BTW /etc/init.d/rcS will add the start as $1 for the links that aren't
> *.sh, so I should just have to put the link in the rcS directory.
If you check /etc/inittab it will tell you the runlevel you start in:
# The default runlevel.
id:3:initdefault:
This is a clue to which of the various /etc/rc?.d directories are appropriate
for you. The example above says I start in runlevel three, so the symbolic
links in /etc/rc3.d are for the various services that run on my system.
For our discussion the file /etc/rc3.d/S23ntp is what we're looking for.
~# ls -l /etc/rc3.d/S23ntp
lrwxrwxrwx 1 root root 13 2007-03-05 11:33 /etc/rc3.d/S23ntp -> ../init.d/ntp
So it's a symbolic link to /etc/init.d/ntp and since it is named S23ntp it is
a startup file. The configuration file for /etc/init.d/ntp is /etc/ntp.conf.
If you enter the following lines
server 0.pool.ntp.org
server 1.pool.ntp.org
server 2.pool.ntp.org
server 3.pool.ntp.org
and then issue the command "/etc/init.d/ntp start" as root, it will start the
local ntp server and sync your clock. If you don't already have the
appropriate symbolic links in /etc/rc[yourrunleve].d, then create them, and it
will start every time your system boots up.
Someone else may be able to clarify anything I made muddy.
--
Neil Schneider pacneil_at_linuxgeek_dot_net
http://www.paccomp.com
Key fingerprint = 67F0 E493 FCC0 0A8C 769B 8209 32D7 1DB1 8460 C47D
"Work to eat, eat to live, live to bike, bike to work." -- Naomi Bloom
--
[email protected]
http://www.kernel-panic.org/cgi-bin/mailman/listinfo/kplug-newbie
