Nick Rout wrote:
[snip]
you shouldn't need to ever reboot unless you get a new kernel, but nevertheless I think it might help this time.
[snip]
Come on now... let's get real. Linux isn't perfect, nor is plenty of the software that runs on it. If you want to lock up your machine, it's pretty simple.
In this case, it looks like the system time is incorrect. I recommend installing ntpdate, which you run on bootup through a script in /etc/init.d, with its associated symlinks. THis takes care of gross inaccuracies. If you've got an always on connection, which I think you have, you may want to play with ntp, to keep the time synched to millisecond accruacy or better.
Once you've done that, you can set yourself up as a tier 3 time server for your local network... and, of course, tommorow, the world (:
Steve.
Note that as your clock is currently in the future, you may get some strange error messages until it unwinds itself. This will especially manifest itself when compiling code, as the makefiles will be well upset.
