Be aware that setting the time so far in the future is dangerous - this adjtime thing is just one possible symptom. I would suggest doing a find across the whole system and manually identify and correct any files you find. Log and other files get created with dates far in the future which can confuse things no end: in fact a couple of years ago it was almost terminal if a system was let run in this state for a few hours.
In most cases, systems usually run in this state for a few minutes, or the time involved is only minutes/days and is quickly passed by, but you have gone a bit too far ... unless you want to wait two months for it to catch up! BillK On Mon, 2003-11-24 at 04:57, SN wrote: > Did I say something about windows? > > I only run gentoo on this box. > As I said before, it ran for month, then some days ago I used the kde tool > to change only the date, I just set the date forward for two month, because > I wanted to test an application I wrote. I did a reboot tested my app, > changed the date back went to bed, next day I realized time was off, date > was still correct, timezone setting in kde was fine, timezone setting in > rc.conf was still okay. > So on everyboot the time was set back by 11 hours, deleting the /etc/adjtime > file fixed it, it was created automatically again and is fine now. > > -- [EMAIL PROTECTED] mailing list
