On 2013-05-24 02:16, brian m. carlson wrote:
Yes, systemd uses separate processes, but they are not independent. They cannot be independently turned off. If I decide I do not want the journal features, however useful others might think they are, I should not have to resort to chmod and dpkg-statoverride to keep them from running. Let them be optional features which the core systemd can be used without.
Well, one central feature for debugging is that "systemctl status $foo.service" gives you the output (stdout/stderr) of that service. This seems to be realized using journald. So that's one case where a feature is realized by a helper binary (it is not in */bin, but in a lib directory). I guess that the syslog-related features can be turned off using journald.conf.
Kind regards Philipp Kern -- To UNSUBSCRIBE, email to debian-devel-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/57f947876efb9a8429d5b2f19b2a1...@hub.kern.lc
