possibly problem with rawhide (systemd-217?): "Found ordering cycle on basic.target/start"

Kevin Fenzi kevin at scrye.com
Fri Oct 31 14:42:55 UTC 2014


On Fri, 31 Oct 2014 14:01:12 +0100
Lennart Poettering <mzerqung at 0pointer.de> wrote:

> So the problem appears to be that gssproxy.service been ordered before
> remote-fs-pre.target. That target is ordered before
> basic.target. However gssproxy.service also is ordered after
> basic.target (simply because all services by default are ordered
> before basic.target, unless they explicitly specify
> DefaultDependencies=no), hence there's an ordering cycle.
> 
> Most likely some NFS maintainers tried to move gss-proxy.service into
> the early boot, and didn't set DefaultDependencies=no.
> 
> That said, services running in early boot must be written in a
> specific style (i.e. not assume /var to be around, and suchlike), I
> do wonder if gssproxy is ready for that.
> 
> Anyway, long story short: file a bug against the gssproxy package.

I don't think this explains all the problems folks are having with
systemd-217. 

I have gssproxy disabled here and still see loops and issues. 
I did not with 216. gssproxy itself hasn't been updated in a long time. 

Happy to provide info from my install here, what info would be good to
get from everyone?

Perhaps in bug would be a better place to collect it: 

https://bugzilla.redhat.com/show_bug.cgi?id=1159117

kevin


-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 819 bytes
Desc: not available
URL: <http://lists.fedoraproject.org/pipermail/devel/attachments/20141031/6cade4c6/attachment.sig>


More information about the devel mailing list