Time Updates

[Larry Hartman]

> OK, somebody who is henceforth forever plonked thinks it's appropriate to
> disagree with this statement in private email.  If I wanted to have private
> discussions with you I wouldn't be on a mailing list.
>
> So, it's got nothing to do with the fact that you can download an ntp
> package that's just about exactly the size of ntpdate.  It's got to do with
> the fact that it's a SERVER.  If you don't know what you're doing, and you
> start running servers, some network admins are going to get a little ticked
> off with you.  On top of that, it's a server that's always doing something.
> It's just more processes that a normal user doesn't need.  For a normal
> user, with a normal computer, running ntpdate every time you power up,
> configure a network interface, or at least every 24 hours, will keep your
> machine close enough to universal time that you won't know the difference.
> --
> derek

My intuition was leading me to the same conclusion, server not the best 
solution, but not so succinct as you made it here.

A comment made in the other thread on this topic leads me in another 
direction...

Art stated:

> Ubuntu gets network time at boot.  If this is a WiFi issue and your WiFi
> isn't connected until you log in to KDE, you need to either run it manually
> or set it up as a periodic cron job.

I am running WICD rather than KNetworkManager because it works much better for 
my wifi model.  It does not seem to set up its connection until late in the 
user login process.  Could this be the culprit?  If so, will your edits to 
the NTPdate config file work in this situation?


Larry