Your message dated Sat, 14 May 2016 20:41:48 +0200
with message-id <[email protected]>
and subject line Re: Bug#824343: services don't start if legacy init script is
a symlink to other filesystem
has caused the Debian Bug report #824343,
regarding services don't start if legacy init script is a symlink to other
filesystem
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.)
--
824343: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=824343
Debian Bug Tracking System
Contact [email protected] with problems
--- Begin Message ---
Package: systemd
Version: 215-17+deb8u4
Severity: important
If the init script in /etc/init.d is a symlink to a script on another
filesystem such as /opt then systemd silently ignores it
It doesn't get started at boot
Using a command like
systemctl start foo
gives no output, no error, but doesn't start it.
Using
systemctl daemon-reload
finds it and starts it.
A workaround is to copy such scripts to /etc/init.d
Even if it can't be fixed to automatically use such scripts, maybe it
should show meaningful errors in this situation
--- End Message ---
--- Begin Message ---
Version: 227-1
Am 14.05.2016 um 19:24 schrieb Daniel Pocock:
> Package: systemd
> Version: 215-17+deb8u4
> Severity: important
>
> If the init script in /etc/init.d is a symlink to a script on another
> filesystem such as /opt then systemd silently ignores it
Having scripts in /opt (or other directories) is not a good idea since
those directories can be on different partitions (not uncommon) for /opt.
systemd needs to be able to read all services to compute its dependency
graph before it starts any services.
> It doesn't get started at boot
>
> Using a command like
>
> systemctl start foo
>
> gives no output, no error, but doesn't start it.
>
> Using
>
> systemctl daemon-reload
>
> finds it and starts it.
>
> A workaround is to copy such scripts to /etc/init.d
I wouldn't consider this a workaround, but the best possible fix.
> Even if it can't be fixed to automatically use such scripts, maybe it
> should show meaningful errors in this situation
See
https://github.com/systemd/systemd/issues/2772
https://github.com/systemd/systemd/pull/1249
Upstream systemd now tries to follow symlinks for the sysv-generator,
that obviously only works if those symlinks don't point to separate file
systems (which aren't mounted yet).
Marking as done for version 227-1
Rergards,
Michael
--
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 ---
_______________________________________________
Pkg-systemd-maintainers mailing list
[email protected]
http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-systemd-maintainers
