F19 Chrony fails to start

2013-07-13 Thread Frank Murphy
Cannot get chronyd.service to start after fedup F18 > F19 I don't know what mdmonitor has to do with it, no raid on box. journalctl -xn -- Logs begin at Thu 2013-07-11 13:15:03 IST, end at Sat 2013-07-13 09:29:41 IST. -- Jul 13 09:29:41 my.upgraded.pc systemd[1]: Cannot add dependency job for un

Re: F19 Chrony fails to start

2013-07-13 Thread Ed Greshko
On 07/13/13 18:33, Frank Murphy wrote: > Cannot get chronyd.service to start after fedup F18 > F19 > > I don't know what mdmonitor has to do with it, no raid on box. > > > journalctl -xn > -- Logs begin at Thu 2013-07-11 13:15:03 IST, end at Sat 2013-07-13 > 09:29:41 IST. -- Jul 13 09:29:41 my.upgr

SOLVED Re: F19 Chrony fails to start

2013-07-13 Thread Frank Murphy
On Sat, 13 Jul 2013 19:01:31 +0800 Ed Greshko wrote: > To fix this problem create the file /etc/sysconfig/chronyd with the > contents > > OPTIONS= -4 > Sorted Thanks Ed, -- Regards, Frank "When in doubt PANIC!" I check for new mail app. 20min www.frankly3d.com -- users mailing list use