Re: 'net time server

>> sat. 4th may 2002 =)
>> which is causing problems upgrading packages due to the fact that emerge
>> thinks the new upgrade is older than the original package

Yes, many programs break if they see the system clock going backwards. In this 
case it has been turned backwards by 4 months.

> Hi James,
> 	I have the following entry in my crontab, which syncs the
> systems time every hour.
>
> 0 * * * * /usr/bin/ntpdate time.demon.co.uk >> /var/log/cron.log

Eeeek - dont do that. If your clock is running fast then this script will keep 
setting your system clock backwards every hour. It might only be a few 
milliseconds, rather than 4 months, but it can still cause problems.

Its ok to do that once, early in the boot scripts, if your system clock is 
very wrong after boot. If you want to keep your clock in sync then run the 
ntp daemon.

I hope this helps