Your message dated Sat, 25 May 2013 15:53:06 +0200
with message-id <[email protected]>
and subject line Re: Bug#709780: Provide a way to not start a daemon on boot
has caused the Debian Bug report #709780,
regarding Provide a way to not start a daemon on boot
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact [email protected]
immediately.)
--
709780: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=709780
Debian Bug Tracking System
Contact [email protected] with problems
--- Begin Message ---
Package: systemd
Version: 44-11
Severity: wishlist
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA256
Hi!
With classis SysV init, we can prevent a daemon to be started on boot
by replacing the symlink from S* to K* in the appropriate
runlevel. This does not seem to work with systemd. Therefore, we are
left with `systemctl mask` and `systemctl unmask`. However, `systemctl
mask` also prevents a deaemon to be started manually (either with
`/etc/init.d/XXXX start` or with `systemctl start XXXX.service`).
Please, document how a daemon should be disabled at boot.
- -- System Information:
Debian Release: jessie/sid
APT prefers unstable
APT policy: (500, 'unstable'), (500, 'testing'), (500, 'stable'), (101,
'experimental')
Architecture: amd64 (x86_64)
Foreign Architectures: i386
Kernel: Linux 3.8-2-amd64 (SMP w/2 CPU cores)
Locale: LANG=fr_FR.utf8, LC_CTYPE=fr_FR.utf8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Versions of packages systemd depends on:
ii dpkg 1.16.10
ii initscripts 2.88dsf-41
ii libacl1 2.2.52-1
ii libaudit0 1:1.7.18-1.1
ii libc6 2.17-3
ii libcap2 1:2.22-1.2
ii libcryptsetup4 2:1.4.3-4
ii libdbus-1-3 1.6.10-1
ii libkmod2 9-3
ii liblzma5 5.1.1alpha+20120614-2
ii libpam0g 1.1.3-9
ii libselinux1 2.1.13-2
ii libsystemd-daemon0 44-11
ii libsystemd-id128-0 44-11
ii libsystemd-journal0 44-11
ii libsystemd-login0 44-11
ii libudev0 175-7.2
ii libwrap0 7.6.q-24
ii udev 175-7.2
ii util-linux 2.20.1-5.4
Versions of packages systemd recommends:
ii libpam-systemd 44-11
Versions of packages systemd suggests:
ii python 2.7.3-5
ii python-cairo 1.8.8-1+b2
ii python-dbus 1.2.0-1
pn systemd-gui <none>
- -- no debconf information
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.12 (GNU/Linux)
iQIcBAEBCAAGBQJRoKl3AAoJEJWkL+g1NSX566QP/3QhFyotneTmOGLuMJWYwo4I
77WJmrjiIETevWicNlozSYum6t7fAYYVn8D7xd7em9ym4TWn5qQfpXvsWZgDO77u
1qCYTnefd0oq4p8gk4wPTmPFti7sw/Vzfh31QVfPHY4MkFjSTEGcCJceABmz1/Wi
B6RLXEpvKsmByBwqkTayiiidAq+7qm5atjdRlo5X2BujXNci/Yq7KO4dS1xyUnrj
U6HsfZoB7f9uU0yhv+36Fb/noqy3DIm//gKT0u6NlMoRQ6jEuzFOwpVDBNRqkQAo
+dtboChO3c8yvW+TDgDO0V1g0tXDC4sB3HiRzmZCBvF07g0zLQaJaYMzLaMCLfZN
MniWZtu5QgXUU1I4FvUSz1gSWvlhwAwo8TLS6kuEnoQ3WdCIrHgS/ExWRR6jebQ0
SblIrSzyaVn6y+UlgL9uJg7gwGEHLN1BZkYW1EUFw30AaAkLr9+n5CqCESHIC1Wn
r3eCvjtagkEoDxCA2vOr/o2VyCV95kp4HKfEhfaY+tVWLkCrSGEXMcxx7p6cTm5V
TIuvGcgpUYWdDMFVNyQi0H+PPjllc5a2roHNs0tLubSgfGTx27xjizTSd5RL+qvt
Xc/EJkjitYDnWSMb69u7JXqAYMVVYYvNML6juTe+TEUiUTNkMIzQFGafHYT5BYpA
aNBn7f1+neiHPgrrWyG2
=SBk7
-----END PGP SIGNATURE-----
--- End Message ---
--- Begin Message ---
Hi Vincent,
Am 25.05.2013 14:07, schrieb Vincent Bernat:
> Package: systemd
> Version: 44-11
> Severity: wishlist
>
> Hi!
>
> With classis SysV init, we can prevent a daemon to be started on boot
> by replacing the symlink from S* to K* in the appropriate
> runlevel.
Yeah, the interface to use for that is
update-rc.d foo disable|enable
> This does not seem to work with systemd.
Exactly the same command exists for systemd:
systemctl enable|disable foo.service
That command creates the relevant symlinks, to enable the service. In
most cases that means creating a symlinks in multi-user.target.wants
which is the equivalent to a symlink in /et/rc?.d/
Therefore, we are
> left with `systemctl mask` and `systemctl unmask`. However, `systemctl
> mask` also prevents a deaemon to be started manually (either with
> `/etc/init.d/XXXX start` or with `systemctl start XXXX.service`).
mask should only be used if you want to make it completely impossible to
start a service (as you noted it cannot be started anymore, even manually).
> Please, document how a daemon should be disabled at boot.
See man 7 daemon , section "Activation on Boot" and the referenced
systemd.unit(5) and systemd.special(7).
Cheers,
Michael
--
Why is it that all of the instruments seeking intelligent life in the
universe are pointed away from Earth?
--
Why is it that all of the instruments seeking intelligent life in the
universe are pointed away from Earth?
signature.asc
Description: OpenPGP digital signature
--- End Message ---
