You are not logged in.
Pages: 1
The error started occurring after I decided to set the right time on my bios's clock. I also messed with hwclock a few times to change the time.
sudo: timestamp too far in the future: Nov 6 12:10:40 2008
Is this a really bad thing?
Also, besides installing something like opentpd, what can I do to fix my system's time and date?
Offline
Try deleting /var/lib/hwclock/adjtime and restart your system.
To know or not to know ...
... the questions remain forever.
Offline
bernacher is saying right here if the problem is still remain then change battery(Cell)......
Last edited by arunix (2009-09-20 02:51:15)
Minds are like parachutes. They only function when they are open.
Offline
bernacher is saying right here if the problem is still remain then change battery(Cell)......
Actually, I already did change the battery and I'm still getting the error. What I haven't done is delete that particular file....yet.
Offline
sudo -k
Offline
Actually, I already did change the battery and I'm still getting the error. What I haven't done is delete that particular file....yet.
whts the value of the file ?
Minds are like parachutes. They only function when they are open.
Offline
Already deleted /var/lib/hwclock/adjtime and restarted the comp. Everything's working fine.
Installed openntpd and its taking care of the incorrect time.
The only issue I have left is with the sudoers file. I want to add timestamp_timeout=0 for a little bit of added security but I'm doing something wrong.
Offline
I think the timestamp_timeout=0 line goes along with the defaults
defaults env_reset insults timestamp_timeout=0
does that look right?
Offline
Pages: 1