Re: [cobalt-users] at reboot date is incorrect, apparentlyhwclock --hctosys isn't being executed

[David Thurman <dthurman@xxxxxxxxxxxxxxxxxxxx>]

on 4-24-02 7:16 AM, Andy Brown at andy.brown@xxxxxxxxxxxxx was reported to
have made a statement that said this:

> <snip>
>> on 4-24-02 5:57 AM, Paul Ferwerda at paul@xxxxxxxxxxxx was
>> reported to have made a statement that said this:
>> 
>>> I searched the archives but didn't see an answer.
> -----
>> We have the same issue on our Raq3's.
> 
> Would something like this work, add in above the exit 0 line in
> /etc/sysconfig/network-scripts/ifup-post the following:
> 
> /usr/sbin/ntpdate ntp.demon.co.uk
> (change ntp.demon.co.uk to a local timeserver for you)
> 
> So the end of the file looks like:
> 
> # Notify programs that have requested notification
> ( cd /var/run/netreport || exit
> for i in * ; do
>   [ -f $i ] && \
>     kill -SIGIO $i >/dev/null 2>&1 || \
>       rm -f $i >/dev/null 2>&1
> done
> )
> /usr/sbin/ntpdate ntp.demon.co.uk
> exit 0
> 
> 
> Hopefully that should sync your clock up straight after network
> interfaces/routing comes up, so pretty early on in terms of webserving,
> etc.
> 
> Regards,
> 
> Andy

Thanks Andy. We are going to try that and see if that will cure our problem.
We had a FreeBSD that we use for DNS that was giving us time errors and I
think my programmer did the same thing to that box.
--
Thank you,
David E Thurman
The Web Presence Group
309.676.5688
dthurman@xxxxxxxxxxxxxxxxxxxx
http://www.webpresencegroup.net