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)
Thanks, Franta Hanzlik
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?
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?
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.
Ed Greshko wrote:
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.
'systemctl status chrony-wait.service' : chrony-wait.service - Wait for chrony to synchronize system clock Loaded: loaded (/usr/lib/systemd/system/chrony-wait.service; disabled) Active: inactive (dead) CGroup: name=systemd:/system/chrony-wait.service
It's disabled too. And it looks like this run only chronyc, which perhaps should not start chronyd.(?)
One more thing: I have in /etc/rc.d/rc.local called ntpdate with some external servers (1.cz.pool.ntp.org 2.cz.pool.ntp.org 3.cz.pool.ntp.org). But this should not trigger chronyd, yes?
Am 25.01.2013 12:41, schrieb Frantisek Hanzlik:
Check to see if you have the chrony-wait.service enabled.
'systemctl status chrony-wait.service' : chrony-wait.service - Wait for chrony to synchronize system clock Loaded: loaded (/usr/lib/systemd/system/chrony-wait.service; disabled) Active: inactive (dead) CGroup: name=systemd:/system/chrony-wait.service
It's disabled too. And it looks like this run only chronyc, which perhaps should not start chronyd.(?)
One more thing: I have in /etc/rc.d/rc.local called ntpdate with some external servers (1.cz.pool.ntp.org 2.cz.pool.ntp.org 3.cz.pool.ntp.org). But this should not trigger chronyd, yes?
why do you not type "yum remove chrony" to uninstall this crap as any unused packge should be removed from a system excatly because what you are having: problems which hardly can be triggered by non existing things
i am pretty sure some dbus activation triggers this all these dbus-activations are uncontrollable crap for me if i want a serivice started i enable it, if not i disable it there is nothing in between
Am 25.01.2013 13:00, schrieb Tom Horsley:
On Fri, 25 Jan 2013 12:50:09 +0100 Reindl Harald wrote:
if i want a serivice started i enable it, if not i disable it there is nothing in between
Just remember in systemd that "disable" needs to be spelled "mask". If you spell it "disable" it has almost no effect :-)
and even if - try to mask colord and have fun with your no longer working desktop
at least it was so some months ago as i tried to get rid of this stuff because i hate the growing process count
On 01/25/2013 07:41 PM, Frantisek Hanzlik wrote:
'systemctl status chrony-wait.service' : chrony-wait.service - Wait for chrony to synchronize system clock Loaded: loaded (/usr/lib/systemd/system/chrony-wait.service; disabled) Active: inactive (dead) CGroup: name=systemd:/system/chrony-wait.service
It's disabled too. And it looks like this run only chronyc, which perhaps should not start chronyd.(?)
One more thing: I have in /etc/rc.d/rc.local called ntpdate with some external servers (1.cz.pool.ntp.org 2.cz.pool.ntp.org 3.cz.pool.ntp.org). But this should not trigger chronyd, yes?
It actually does, at least on my system, probably because it has Requires=chronyd.service.
If I have ntpd.service enabled and only chrony-wait.service and reboot my VM it gets started...
[egreshko@f18x ~]$ systemctl status chronyd.service chronyd.service - NTP client/server Loaded: loaded (/usr/lib/systemd/system/chronyd.service; disabled) Active: active (running) since Fri 2013-01-25 21:07:17 CST; 1min 1s ago Process: 682 ExecStartPost=/usr/libexec/chrony-helper add-dhclient-servers (code=exited, status=0/SUCCESS) Process: 647 ExecStart=/usr/sbin/chronyd -u chrony $OPTIONS (code=exited, status=0/SUCCESS) Process: 602 ExecStartPre=/usr/libexec/chrony-helper generate-commandkey (code=exited, status=0/SUCCESS) Main PID: 676 (chronyd) CGroup: name=systemd:/system/chronyd.service └─676 /usr/sbin/chronyd -u chrony
[egreshko@f18x ~]$ systemctl status chrony-wait.service chrony-wait.service - Wait for chrony to synchronize system clock Loaded: loaded (/usr/lib/systemd/system/chrony-wait.service; enabled) Active: active (exited) since Fri 2013-01-25 21:07:47 CST; 1min 8s ago Process: 684 ExecStart=/usr/bin/chronyc waitsync 60 0.1 (code=exited, status=0/SUCCESS)
[egreshko@f18x ~]$ systemctl status ntpd.service ntpd.service - Network Time Service Loaded: loaded (/usr/lib/systemd/system/ntpd.service; enabled) Active: inactive (dead)
ntpd didn't get started since it lost the race to get the port.
Anyway, I'd just go ahead and remove chrony from the system if you're not going to use it.
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1
On 01/25/2013 06:41 AM, Frantisek Hanzlik wrote:
Ed Greshko wrote:
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.
'systemctl status chrony-wait.service' : chrony-wait.service - Wait for chrony to synchronize system clock Loaded: loaded (/usr/lib/systemd/system/chrony-wait.service; disabled) Active: inactive (dead) CGroup: name=systemd:/system/chrony-wait.service
It's disabled too. And it looks like this run only chronyc, which perhaps should not start chronyd.(?)
One more thing: I have in /etc/rc.d/rc.local called ntpdate with some external servers (1.cz.pool.ntp.org 2.cz.pool.ntp.org 3.cz.pool.ntp.org). But this should not trigger chronyd, yes?
No idea why this is starting up, but could you attach the output of.
sealert -l b7fea8ae-73b7-4588-aac7-36d4d5b69281
Daniel J Walsh wrote: ...
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
No idea why this is starting up, but could you attach the output of.
sealert -l b7fea8ae-73b7-4588-aac7-36d4d5b69281
In meantime this PC was rebooted and maybe therefore this alert isn't found yet, it gives output: query_alerts error (1003): id (b7fea8ae-73b7-4588-aac7-36d4d5b69281) not found
But perhaps same and newer alert:
sealert -l 268e2d9b-d891-47d5-8b44-07e0678871a8 SELinux is preventing /usr/sbin/chronyd from module_request access on the system .
***** Plugin disable_ipv6 (91.4 confidence) suggests ***********************
If you want to disable IPV6 on this machine Then you need to set /proc/sys/net/ipv6/conf/all/disable_ipv6 to 1 and do not blacklist the module' Do add net.ipv6.conf.all.disable_ipv6 = 1 to /etc/sysctl.conf
***** Plugin catchall (9.59 confidence) suggests ***************************
If you believe that chronyd should be allowed module_request access on the system by default. Then you should report this as a bug. You can generate a local policy module to allow this access. Do allow this access for now by executing: # grep chronyd /var/log/audit/audit.log | audit2allow -M mypol # semodule -i mypol.pp
Additional Information: Source Context system_u:system_r:chronyd_t:s0 Target Context system_u:system_r:kernel_t:s0 Target Objects [ system ] Source chronyd Source Path /usr/sbin/chronyd Port <Neznámé> Host pc.my.home Source RPM Packages chrony-1.27-0.3.pre1.fc17.i686 Target RPM Packages Policy RPM selinux-policy-3.10.0-166.fc17.noarch Selinux Enabled True Policy Type targeted Enforcing Mode Permissive Host Name pc.my.home Platform Linux pc.my.home 3.6.11-5.fc17.i686.PAE #1 SMP Tue Jan 8 21:49:19 UTC 2013 i686 i686 Alert Count 2 First Seen 2013-01-24 11:49:10 CET Last Seen 2013-01-24 11:49:39 CET Local ID 268e2d9b-d891-47d5-8b44-07e0678871a8
Raw Audit Messages type=AVC msg=audit(1359024579.623:91): avc: denied { module_request } for pid=753 comm="chronyd" kmod="net-pf-10" scontext=system_u:system_r:chronyd_t:s0 tcontext=system_u:system_r:kernel_t:s0 tclass=system
type=SYSCALL msg=audit(1359024579.623:91): arch=i386 syscall=socketcall success=no exit=EAFNOSUPPORT a0=1 a1=bf9065a0 a2=b76bbff4 a3=bf906694 items=0 ppid=1 pid=753 auid=4294967295 uid=983 gid=979 euid=983 suid=983 fsuid=983 egid=979 sgid=979 fsgid=979 tty=(none) ses=4294967295 comm=chronyd exe=/usr/sbin/chronyd subj=system_u:system_r:chronyd_t:s0 key=(null)
Hash: chronyd,chronyd_t,kernel_t,system,module_request
audit2allow
#============= chronyd_t ============== #!!!! This avc can be allowed using the boolean 'domain_kernel_load_modules'
allow chronyd_t kernel_t:system module_request;
audit2allow -R
#============= chronyd_t ============== #!!!! This avc can be allowed using the boolean 'domain_kernel_load_modules'
allow chronyd_t kernel_t:system module_request;
~~~~~~~~~
But sealert reccomendation isn't useful in this case, as I've IPv6 disabled at kernel commandline (ipv6.disable=1) and directory /proc/sys/net/ipv6/ does not exist. Is there any better solution? (I maybe could disable SELinux as this PC is in internal LAN and SELinux is even in permissive mode. But I'm still in hope that someday will understand it this ;)
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1
Ok, so you are disabling ipv6.
I wrote a blog on this in the past.
http://danwalsh.livejournal.com/47118.html
Ed Greshko wrote:
On 01/25/2013 07:41 PM, Frantisek Hanzlik wrote:
'systemctl status chrony-wait.service' : chrony-wait.service - Wait for chrony to synchronize system clock Loaded: loaded (/usr/lib/systemd/system/chrony-wait.service; disabled) Active: inactive (dead) CGroup: name=systemd:/system/chrony-wait.service
It's disabled too. And it looks like this run only chronyc, which perhaps should not start chronyd.(?)
One more thing: I have in /etc/rc.d/rc.local called ntpdate with some external servers (1.cz.pool.ntp.org 2.cz.pool.ntp.org 3.cz.pool.ntp.org). But this should not trigger chronyd, yes?
It actually does, at least on my system, probably because it has Requires=chronyd.service.
If I have ntpd.service enabled and only chrony-wait.service and reboot my VM it gets started...
[egreshko@f18x ~]$ systemctl status chronyd.service chronyd.service - NTP client/server Loaded: loaded (/usr/lib/systemd/system/chronyd.service; disabled) Active: active (running) since Fri 2013-01-25 21:07:17 CST; 1min 1s ago Process: 682 ExecStartPost=/usr/libexec/chrony-helper add-dhclient-servers (code=exited, status=0/SUCCESS) Process: 647 ExecStart=/usr/sbin/chronyd -u chrony $OPTIONS (code=exited, status=0/SUCCESS) Process: 602 ExecStartPre=/usr/libexec/chrony-helper generate-commandkey (code=exited, status=0/SUCCESS) Main PID: 676 (chronyd) CGroup: name=systemd:/system/chronyd.service └─676 /usr/sbin/chronyd -u chrony
[egreshko@f18x ~]$ systemctl status chrony-wait.service chrony-wait.service - Wait for chrony to synchronize system clock Loaded: loaded (/usr/lib/systemd/system/chrony-wait.service; enabled) Active: active (exited) since Fri 2013-01-25 21:07:47 CST; 1min 8s ago Process: 684 ExecStart=/usr/bin/chronyc waitsync 60 0.1 (code=exited, status=0/SUCCESS)
[egreshko@f18x ~]$ systemctl status ntpd.service ntpd.service - Network Time Service Loaded: loaded (/usr/lib/systemd/system/ntpd.service; enabled) Active: inactive (dead)
ntpd didn't get started since it lost the race to get the port.
Anyway, I'd just go ahead and remove chrony from the system if you're not going to use it.
Thus I have not skip over, but creep under? In this case uninstalling chronyd isn't problem, but I can imagine some situation where I want some service being installed, but started only in specific situations. Apparently is time for learning how debug and live with D-bus.
Present Fedora advancement fairly shrink me, as there is several things which are unfinished, unreliable and erroneous in certain situations (in particular systemd, pulseaudio, sssd, d-bus, ...). I hope they are cripled only by implementation, not by design; and situation will be with time better... In other case we will have there unstable bastard like windows (now just binary logs are missing;) - I sometimes say oneself, whether at Linux now aren't working designated/canned peoples from windows ;)
Daniel J Walsh wrote:
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1
Ok, so you are disabling ipv6.
I wrote a blog on this in the past.
When I perceive this blog correctly, then this IPv6 problem still has not clean solution. But IMO (sorry I'm not programmer), when program has any option for not using this protocol (e.g "-4" cmdline switch for "Use IPv4 only" operation) or is smart enough for detecting disabled IPv6 etc, then there should be no reason for loading ipv6 kernel modules. Or I'm wrong?
-
Daniel J Walsh -
Ed Greshko -
Franta Hanzlík -
Reindl Harald -
Tom Horsley