mirror of
https://github.com/systemd/systemd.git
synced 2024-11-05 15:21:37 +03:00
0ce8860a15
On systemd systems seasoned admins might be surprised to see that the init scripts and log files are gone. To ease the transition let's place some README files there, that hopefully help clearing up the situation.
28 lines
1.1 KiB
Plaintext
28 lines
1.1 KiB
Plaintext
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
|
|
http://www.freedesktop.org/wiki/Software/systemd/Incompatibilities
|