systemd: Is it wrong?
Steve Dickson
SteveD at redhat.com
Fri Jul 8 02:57:54 UTC 2011
Hello,
One of the maintainers of systemd and I have been working
together on trying to convert the NFS SysV init scripts
into systemd services. Here is the long trail...
https://bugzilla.redhat.com/show_bug.cgi?id=699040
The point is this, with fairly complicated system,
some events need to have happen, like loading modules,
before other events happen, like setting parameters of
those loaded modules.
Currently the ExecStart commands can be started and end
before the ExecStartPre even start. This means setting
modules parameters within the same service file are
impossible.
I suggested that a boundary be set that all ExecStartPre
commands finish before any ExecStart commands start,
which would allow complicated subsystems, like NFS,
to start in a very stable way...
So is it wrong? Shouldn't there away to allow certain
parts of a system to synchronously configure some
things so other parts will come up as expected?
tia,
steved.
More information about the devel
mailing list