*** This bug is a duplicate of bug 43233 ***
https://bugs.launchpad.net/bugs/43233
Incidentally, I just had this same problem with my old pentium II. It's
a headless server that primarily runs mpd for our music on hold. I
logged in through ssh and changed the network so that I could run apt-
get for updates after changing the network structure at the office. I
had no problems until the network successfully connected to the
internet. Then, I was getting the "sudo timestamp to far in the
future..." error.
>From an ssh terminal on a headless server I could not change the time
without running ssh. I threw up my hands and went to do something else.
I cam back an hour or two later and voila, it worked fine. Something
happened within that time to resolve the error, and I wonder if it
wasn't just a ntpdate update or something like that.
--
sudo: timestamp too far in the future
https://bugs.launchpad.net/bugs/76639
You received this bug notification because you are a member of Ubuntu
Bugs, which is the bug contact for Ubuntu.
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
