On Thursday, June 20, 2013 02:38:37 PM Colin Walters wrote:
On Thu, 2013-06-20 at 13:15 -0500, Chris Adams wrote:
> I think most "traditional" system admins see a running NM daemon as an
> additional point of failure in a static network. If my server's network
> setup is static, I don't want a daemon running attempting to "manage"
> it. If it has a bug, gets misconfigured, etc., it might do something to
> screw up an otherwise working setup.
Yes, it's just not easy to do without creating race conditions. Various
other components use NetworkManager as an API, and if just called exit()
arbitrarily it'd introduce the problems described here:
https://bugs.freedesktop.org/show_bug.cgi?id=11454
This point has been raised repeatedly, the developers are aware that
it'd be nicer for NM to not show up in "ps" in these situations, but the
reason it's not done is it's nontrivial and there are a lot of other
things in the priority queue.
Maybe split off all functionality from the dbus daemon into separate binaries (off the top
of
my head, about a dozen, each in a separate package) and the dbus daemon uses system() to
invoke the appropriate one when requested. Servers would just dispense with the daemon
and invoke binaries directly in a startup script.
Davide Bolcioni