If you reboot, systemd will be used instead of the default init script.
Currently debians version of systemd doesn't ship many service files by default. Systemd
will automaticly fallback to the lsb script, if a service file for a deamon is
missing. So the speedup isn't as big as on other distributions such as archlinux
or fedora, which provide a deeper integration.
To get a quick overview, which services are started nativly, type the following command:
$ systemctl list-units
All descriptions containing `LSB: ` are launched through lsb scripts.
Writing your own service files, is straight forward. If you add custom service
files, put them in /etc/systemd/system, so they will not get overwritten by
updates.
To get further information about systemd, I recommend the [great archlinux wiki article](https://wiki.archlinux.org/index.php/Systemd).
At the end of this article, I provide some basic one, I use. I port them over mostly from archlinux.
In the most cases, i just have adjusted the path of the binary to get them working. (from /usr/bin to /usr/sbin for ex.)
It is important, that the service name match with the initscript, so it will be used instead by systemd.
This will not work in all cases like dhcpcd which contains the specific network device (like dhcpcd@eth0). In this case, you have to remove origin service with `update-rc.d` and enable the service file with `systemctl enable`.
Also avaible as [gist](https://gist.github.com/ac8ab2e84125ededa5c5):
``` plain /etc/systemd/system/dhcpcd@.service
# IMPORTANT: only works with dhcpcd5 not the old dhcpcd3!
[Unit]
Description=dhcpcd on %I
Wants=network.target
Before=network.target
[Service]
Type=forking
PIDFile=/run/dhcpcd-%I.pid
ExecStart=/sbin/dhcpcd -A -q -w %I
ExecStop=/sbin/dhcpcd -k %I
[Install]
Alias=multi-user.target.wants/dhcpcd@eth0.service
```
``` plain /etc/systemd/system/monit.service
[Unit]
Description=Pro-active monitoring utility for unix systems