Hi,
if the time difference is too big, NTP will refuse to touch the clock
altogether. You can force an update by the '-g' option. However,
the adjustment might still be slow. I'd do the following (as root):
# hwclock --set --utc --date="2014-01-14 22:05:35"
# ntpd -qg
The first command manually sets the hardware clock to the approximate
correct time (which you should adjust, of course). Note that the date
string must specify the time in your local timezone, despite the '--utc'
option.
The second command tells NTP to do a one-shot sync ('-q') and allow an
initial big adjustment ('-g').
Then, for the future, just make sure you have the NTP daemon enabled to
keep the clock in sync. On Debian, if you have installed the 'ntp'
package, this should be fine.
Happy Hacking
Moritz
Jeroen Massar <jeroen@xxxxxxxxx> writes:
> On 2014-01-14 21:05, I wrote:
>> Jeroen,
>>
>> Thank you. It did that but I can't see a change.
>
> NTP adjusts slowly, as your clock is 6+ hours off, you should force the
> timesync first, eg with with rdate (apt-get install rdate):
>
> rdate -v ntp.xs4all.nl
>
> should do the trick. Then after that make sure that ntpd is running:
> /etc/init.d/ntp restart
>
>> The VPS person said it is set to UTC. Previously on another VPS it
>> was another relay in the ?circuit which had the time difference.
>
> UTC is a timezone, and having that is great as it avoids all the
> pitfalls and annoyances with summer/winter time.
>
> Note that some VPSs do not allow changing of the time, one will have to
> ask the host to set the time.
>
> Do note that a VPS can be inspected and controlled easily by the Host,
> as such, make sure that you trust that operator.
>
> Greets,
> Jeroen
--
OpenPGP:
Public Key: http://openpgp.klammler.eu
Fingerprint: 80C1 EC79 B554 3D84 0A35 A728 7057 B288 CE61 2235
Attachment:
pgpFgWg3Lkx1l.pgp
Description: PGP signature
_______________________________________________ tor-relays mailing list tor-relays@xxxxxxxxxxxxxxxxxxxx https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-relays