192 |
- |
1 |
You are looking for the traditional init scripts in /etc/rc.d/init.d,
|
|
|
2 |
and they are gone?
|
|
|
3 |
|
|
|
4 |
Here's an explanation on what's going on:
|
|
|
5 |
|
|
|
6 |
You are running a systemd-based OS where traditional init scripts have
|
|
|
7 |
been replaced by native systemd services files. Service files provide
|
|
|
8 |
very similar functionality to init scripts. To make use of service
|
|
|
9 |
files simply invoke "systemctl", which will output a list of all
|
|
|
10 |
currently running services (and other units). Use "systemctl
|
|
|
11 |
list-unit-files" to get a listing of all known unit files, including
|
|
|
12 |
stopped, disabled and masked ones. Use "systemctl start
|
|
|
13 |
foobar.service" and "systemctl stop foobar.service" to start or stop a
|
|
|
14 |
service, respectively. For further details, please refer to
|
|
|
15 |
systemctl(1).
|
|
|
16 |
|
|
|
17 |
Note that traditional init scripts continue to function on a systemd
|
|
|
18 |
system. An init script /etc/rc.d/init.d/foobar is implicitly mapped
|
|
|
19 |
into a service unit foobar.service during system initialization.
|
|
|
20 |
|
|
|
21 |
Thank you!
|
|
|
22 |
|
|
|
23 |
Further reading:
|
|
|
24 |
man:systemctl(1)
|
|
|
25 |
man:systemd(1)
|
|
|
26 |
http://0pointer.de/blog/projects/systemd-for-admins-3.html
|
|
|
27 |
https://www.freedesktop.org/wiki/Software/systemd/Incompatibilities
|