On 01/25/2013 06:42 PM, Frantisek Hanzlik wrote: > Ed Greshko wrote: >> On 01/25/2013 04:22 PM, Frantisek Hanzlik wrote: >>> At F17 i386 I have both ntp and chrony package installed, ntpd daemon >>> is enabled and chronyd daemon is disabled. Despite of this, something >>> causes chronyd to start. How I can determine how and why it is? >>> (Please, I do not want hints as masking chronyd/uninstalling chrony) >>> >> Are you saying that chronyd is running immediately after boot or sometime later? > It appears as chronyd started immediately after boot, messages > says it start at same time as logger: > > Jan 23 07:12:37 pc kernel: imklog 5.8.10, log source = /proc/kmsg started. > Jan 23 07:12:37 pc chronyd[775]: Frequency 89.081 +/- 14.761 ppm read from /var/lib/chrony/drift > Jan 23 07:12:37 pc kernel: [ 1.489629] ehci_hcd 0000:00:12.2: USB 2.0 started, EHCI 1.00 > Jan 23 07:12:37 pc kernel: [ 1.497698] ehci_hcd 0000:00:13.2: USB 2.0 started, EHCI 1.00 > Jan 23 07:12:38 pc polkitd[904]: started daemon version 0.104 using authority implementation `local' version `0.104' > Jan 23 07:12:41 pc setroubleshoot: SELinux is preventing /usr/sbin/chronyd from module_request access on the system . For complete SELinux messages. run > sealert -l b7fea8ae-73b7-4588-aac7-36d4d5b69281 > Jan 23 07:13:06 pc setroubleshoot: SELinux is preventing /usr/sbin/chronyd from module_request access on the system . For complete SELinux messages. run > sealert -l b7fea8ae-73b7-4588-aac7-36d4d5b69281 > Jan 23 07:13:11 pc chronyd[775]: Selected source 89.31.8.3 > Jan 23 07:13:11 pc chronyd[775]: System clock wrong by 0.646634 seconds, adjustment started > Jan 23 07:13:12 pc chronyd[775]: Selected source 195.113.159.1 > > and: > > 'systemctl status chronyd.service' : > chronyd.service - NTP client/server > Loaded: loaded (/usr/lib/systemd/system/chronyd.service; disabled) > Active: inactive (dead) > CGroup: name=systemd:/system/chronyd.service > > Jan 25 09:00:49 pc.my.home chronyd[753]: NTP packet received from unauthorised host 192.168.1.75 port 1658 > Jan 25 09:01:04 pc.my.home chronyd[753]: NTP packet received from unauthorised host 192.168.1.75 port 1658 > Jan 25 09:01:20 pc.my.home chronyd[753]: NTP packet received from unauthorised host 192.168.1.75 port 1024 > Jan 25 09:01:35 pc.my.home chronyd[753]: NTP packet received from unauthorised host 192.168.1.75 port 1024 > Jan 25 09:02:21 pc.my.home chronyd[753]: NTP packet received from unauthorised host 192.168.1.75 port 1658 > Jan 25 09:02:36 pc.my.home chronyd[753]: NTP packet received from unauthorised host 192.168.1.75 port 1658 > Jan 25 09:02:51 pc.my.home chronyd[753]: NTP packet received from unauthorised host 192.168.1.75 port 1658 > Jan 25 09:03:06 pc.my.home chronyd[753]: NTP packet received from unauthorised host 192.168.1.75 port 1024 > Jan 25 09:03:21 pc.my.home chronyd[753]: NTP packet received from unauthorised host 192.168.1.75 port 1024 > Jan 25 09:04:05 pc.my.home chronyd[753]: chronyd exiting > > (chronyd isn't running as i stopped it) > > Any idea why chronyd has been started? Check to see if you have the chrony-wait.service enabled. -- Programming today is a race between software engineers striving to build bigger and better idiot-proof programs, and the Universe trying to produce bigger and better idiots. So far, the Universe is winning. -- Rick Cook, The Wizardry Compiled -- users mailing list users@xxxxxxxxxxxxxxxxxxxxxxx To unsubscribe or change subscription options: https://admin.fedoraproject.org/mailman/listinfo/users Guidelines: http://fedoraproject.org/wiki/Mailing_list_guidelines Have a question? Ask away: http://ask.fedoraproject.org
