On 10/31/2014 12:57 PM, Matthew Miller wrote: > Oct 31 07:42:29 ubik systemd[1]: Found ordering cycle on basic.target/start > Oct 31 07:42:29 ubik systemd[1]: Found dependency on sysinit.target/start > Oct 31 07:42:29 ubik systemd[1]: Found dependency on systemd-update-utmp.service/verify-active > Oct 31 07:42:29 ubik systemd[1]: Found dependency on systemd-tmpfiles-setup.service/start > Oct 31 07:42:29 ubik systemd[1]: Found dependency on systemd-journal-flush.service/start > Oct 31 07:42:29 ubik systemd[1]: Found dependency on remote-fs.target/start > Oct 31 07:42:29 ubik systemd[1]: Found dependency on remote-fs-pre.target/start > Oct 31 07:42:29 ubik systemd[1]: Found dependency on nfs-client.target/start > Oct 31 07:42:29 ubik systemd[1]: Found dependency on gssproxy.service/start > Oct 31 07:42:29 ubik systemd[1]: Found dependency on basic.target/start > Oct 31 07:42:29 ubik systemd[1]: Breaking ordering cycle by deleting job systemd-update-utmp.service/verify-active This ordering cycle was introduced recently by changes in nfs-utils's unit files when nfs-client.target got an After dependency on gssproxy. nfs-client.target wants to be started before any remote filesystems are mounted (which is before basic.target). gssproxy.service has default dependencies, so it wants to start quite late during boot (after basic.target). [CC Steve.] Regards, Michal -- devel mailing list devel@xxxxxxxxxxxxxxxxxxxxxxx https://admin.fedoraproject.org/mailman/listinfo/devel Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct
