On Tue, 2012-02-28 at 14:10 -0800, jdow wrote:
On 2012/02/28 07:38, Aaron Konstam wrote:
On Mon, 2012-02-27 at 18:06 -0800, Marvin Kosmal wrote:
On Mon, Feb 27, 2012 at 3:17 PM, Patrick Dupre patrick.dupre@york.ac.uk wrote: Hello,
I am runing chrony chronyd.service - NTP client/server Loaded: loaded (/lib/systemd/system/chronyd.service; enabled) Active: active (running) since Mon, 27 Feb 2012 22:42:01 +0100; 35min ago Main PID: 4150 (chronyd) CGroup: name=systemd:/system/chronyd.service └ 4150 /usr/sbin/chronyd -u chrony but my clock is still not on time. How can I synchronize is manually (before I sued to do ntpdate time.server.Run: system-config-date and in the Time Zone display be sure UTC is checked.
Unless somebody broke ntp that last is in no way required. It has never been required. It doesn't even seem to require the motherboard clock to be set to UTC.
{^_^}
Although it is always good to hear from jdow her statement is wrong. Tim Waugh and I spent at least a month trying to debug the fact that on my network printer browsing did not work. After a lot of agony and searching log files we found that the problem was the print client was jumping around in time so the server got confused about the browsing and just gave up. Also ntpd would quit shortly after it was started. The problem was fixed by checking UTC in the system-config-date display.