Systemd

History

Zbigniew Jędrzejewski-Szmek 2c201c2140 meson: use booleans for conf.set and drop unecessary conditionals Using conf.set() with a boolean argument does the right thing: either #ifdef or #undef. This means that conf.set can be used unconditionally. Previously I used '1' as the placeholder value, and that needs to be changed to 'true' for consistency (under meson 1 cannot be used in boolean context). All checks need to be adjusted.		2017-05-02 16:29:11 -04:00
..
.gitignore	docs: install README files into /var/log and 7etc/rc.d/init.d	2012-10-17 21:25:42 +02:00
Makefile	docs: install README files into /var/log and 7etc/rc.d/init.d	2012-10-17 21:25:42 +02:00
README.in	docs: use https:// in URLs	2017-02-21 18:18:24 +01:00
meson.build	meson: use booleans for conf.set and drop unecessary conditionals	2017-05-02 16:29:11 -04:00

README.in

You are looking for the traditional init scripts in @SYSTEM_SYSVINIT_PATH@,
and they are gone?

Here's an explanation on what's going on:

You are running a systemd-based OS where traditional init scripts have
been replaced by native systemd services files. Service files provide
very similar functionality to init scripts. To make use of service
files simply invoke "systemctl", which will output a list of all
currently running services (and other units). Use "systemctl
list-unit-files" to get a listing of all known unit files, including
stopped, disabled and masked ones. Use "systemctl start
foobar.service" and "systemctl stop foobar.service" to start or stop a
service, respectively. For further details, please refer to
systemctl(1).

Note that traditional init scripts continue to function on a systemd
system. An init script @SYSTEM_SYSVINIT_PATH@/foobar is implicitly mapped
into a service unit foobar.service during system initialization.

Thank you!

Further reading:
        man:systemctl(1)
        man:systemd(1)
        http://0pointer.de/blog/projects/systemd-for-admins-3.html
        https://www.freedesktop.org/wiki/Software/systemd/Incompatibilities