Re: Revised systemd Guidelines

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



Toshio Kuratomi (a.badger@xxxxxxxxx) said: 
> 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?

Transparently; if an init.d script is called with 'start', 'stop', 'reload',
'restart', or 'condrestart' (or any synonyms thereof), it's silently
redirected to systemctl if systemd is in use. See the top of
/etc/init.d/functions for details.

> Does this mean that init scripts have to be rewritten
> to do something like this?

No, no initscript changes are required.

Bill
--
packaging mailing list
packaging@xxxxxxxxxxxxxxxxxxxxxxx
https://admin.fedoraproject.org/mailman/listinfo/packaging


[Index of Archives]     [Fedora Users]     [Fedora Desktop]     [Fedora SELinux]     [Big List of Linux Books]     [Yosemite Forum]     [KDE Users]

  Powered by Linux