+++ This bug was initially created as a clone of Bug #741115 +++
--- Additional comment from john.ellson on 2011-09-29 13:08:44 EDT
Why doesn't systemd detect cycles like this? It seems very fragile if this kind of bug in an unrelated service can make the system near unrecoverable because services like dbus and NetworkManager fail to start.
--- Additional comment from mschmidt on 2011-09-29 16:10:10 EDT
It does. It breaks cycles by dropping a (pretty much randomly selected) member of the cycle. In https://bugzilla.redhat.com/show_bug.cgi?id=741078#c3 I showed an example where dbus.socket was the unfortunate victim.
--- Additional comment from john.ellson on 2011-09-30 09:38:25 EDT
Isn't it a cycle in a directed graph? Shouldn't the strategy be to drop the lowest node in the cycle, rather than a random node ? Or perhaps drop the node with the least dependencies up to that point?
Somehow I think it should cause less damage than it did in this case.
This package has changed ownership in the Fedora Package Database. Reassigning to the new owner of this component.
Some cycle-breaking suggestions in the upstream mailing list thread:
This message is a reminder that Fedora 16 is nearing its end of life.
Approximately 4 (four) weeks from now Fedora will stop maintaining
and issuing updates for Fedora 16. It is Fedora's policy to close all
bug reports from releases that are no longer maintained. At that time
this bug will be closed as WONTFIX if it remains open with a Fedora
'version' of '16'.
Package Maintainer: If you wish for this bug to remain open because you
plan to fix it in a currently maintained version, simply change the 'version'
to a later Fedora version prior to Fedora 16's end of life.
Bug Reporter: Thank you for reporting this issue and we are sorry that
we may not be able to fix it before Fedora 16 is end of life. If you
would still like to see this bug fixed and are able to reproduce it
against a later version of Fedora, you are encouraged to click on
"Clone This Bug" and open it against that version of Fedora.
Although we aim to fix as many bugs as possible during every release's
lifetime, sometimes those efforts are overtaken by events. Often a
more recent Fedora release includes newer upstream software that fixes
bugs or makes them obsolete.
The process we are following is described here: