On Sunday 23 May 2004 10:50 pm, steve wrote: > 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. While it's pretty simple to lock up your X-server and keyboard it's now actually very difficult indeed to bring the machine kernel itself to its knees.
[EMAIL PROTECTED] chris]$ uptime 10:51pm up 86 days, 9:49, 1 user, load average: 0.00, 0.00, 0.00 That's a file, print, and web-server machine. & imho it's only just starting the current run. I turned it off because of a thunderstorm. > 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. This whole exercise is getting a bit beyond a joke. It has at least shown young Caleb that he does not know everything about hardware clocks. Thank you all for your patience. I will ensure the clock is set correctly tomorrow. -- Sincerely etc. Christopher Sawtell NB. This PC runs Linux. If you find a virus apparently from me, it has forged the e-mail headers on someone else's machine. Please do not notify me when this occurs. Thanks.
