El mar, 21 de oct 2014 a las 7:03 , Josselin Mouette <j...@debian.org>
escribió:
The Wanderer <wande...@fastmail.fm> wrote:
This is the problem. The init system should not be providing
"features"
which other software might, post-boot and pre-shutdown, want
to make use
of. (AFAIK sysvinit never did, and most - possibly all? - of
the other
init-system candidates don't either.) Such features should be
provided
separately, independent of what may happen to be running as
PID 1.
These features cannot exist separately. Quoting the systemd position
statement:
[…] while it is true that a handful of trivial interfaces are not
really
related to systemd (and could be split out if needed), most of these
features cannot be implemented without close integration to PID 1. It
is
not possible to split the system cgroups arbitrator from the process
which starts services and sessions in cgroups. It is not possible to
ensure the relation of a log to a service if you do not have awareness
of how the service was launched. Et caetera.
Upstart can launch processes in cgroups using cgmanager since version
1.13. Few things are truly impossible with programming, and making
certain functions be implemented independent of or outside of PID 1
does not come close to impossible.
Also, I do not understand the log statement. Once again, Upstart can
hook up a job's stdout/err to a file in /var/log/upstart/, but I am not
exactly sure what was being said so maybe I missed the point.
Cheers,
--
Cameron
