[Author Prev][Author Next][Thread Prev][Thread Next][Author Index][Thread Index]
Re: [tor-bugs] #5633 [Tor Relay]: Clock syncing feature
#5633: Clock syncing feature
-------------------------+--------------------------------------------------
Reporter: cypherpunks | Owner:
Type: enhancement | Status: new
Priority: normal | Milestone: Tor: unspecified
Component: Tor Relay | Version: Tor: unspecified
Keywords: | Parent:
Points: | Actualpoints:
-------------------------+--------------------------------------------------
Comment(by tmpname0901):
> The problem is that a clock can't be accessed or modified by user, even
as root.
I assume that cypherpunks is referring to OpenVZ containers.
I've had a number of OpenVZ containers running Tor. Many had inaccurate
system times, sometimes grossly inaccurate. However I have uniformly
found that VPS vendors will fix the time problem if you inform them of it.
OpenVZ containers get their system time from the host, so if your VPS is
inaccurate that means the host is inaccurate, which in turn means every
container being hosted is inaccurate.
Do this:
1. Set your VPS to the local time zone, e.g.:
# cp -fp /usr/share/zoneinfo/US/Central /etc/localtime; yum -y reinstall
tzdata; reboot
2. Use ntpdate to measure the gap between accurate time and system time,
and send the output to you vendor:
# ntpdate -q 0.us.pool.ntp.org
Try it. I think you'll find that your VPS vendor will realize that fixing
your problem means also fixing their own problem.
--
Ticket URL: <https://trac.torproject.org/projects/tor/ticket/5633#comment:2>
Tor Bug Tracker & Wiki <https://trac.torproject.org/>
The Tor Project: anonymity online
_______________________________________________
tor-bugs mailing list
tor-bugs@xxxxxxxxxxxxxxxxxxxx
https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-bugs