On Fri, Dec 03, 2010 at 02:00:37PM -0500, Bill Nottingham wrote:
> Toshio Kuratomi (a.badger@xxxxxxxxx) said:
> > 1) A system admin unfamiliar with systemd installs apache and sees that
> > there's an /etc/init.d/httpd file. He runs /etc/init.d/httpd start to
> > startup the service unaware that when systemd reboots the service it will be
> > using the unit file and not the sysvinit script.
>
> /etc/init.d/<foo> start redirects to systemctl; systemd will then start
> whichever of the units is 'active' - in this case, it would be the systemd
> service both before and after reboot.
>
How does this work? Does this mean that init scripts have to be rewritten
to do something like this?
start)
systemctl check-that-systemd-is-the-init-system
if test $? ; then
systemctl $1 start
else
# Do startup when running sysvinit/upstart/etc
fi
-Toshio
Attachment:
pgpLF7vxEUr8l.pgp
Description: PGP signature
-- packaging mailing list packaging@xxxxxxxxxxxxxxxxxxxxxxx https://admin.fedoraproject.org/mailman/listinfo/packaging
