Bug#819040: insserv: Symlinked init script in /etc/init.d/<service> fails to be recognised on reboot.

Brett Ryan brett.ryan at gmail.com
Wed Mar 23 14:27:57 GMT 2016



> On 23 Mar 2016, at 22:05, Felipe Sateler <fsateler at debian.org> wrote:
> 
> On Wed, 23 Mar 2016 18:52:20 +1100 Brett Ryan <brett.ryan at gmail.com> wrote:
> > 
> > > On 23 Mar 2016, at 18:39, Petter Reinholdtsen <pere at hungry.com> wrote:
> > > 
> > > When that is said, I suspect it is in general a good idea to not use
> > > symlinks in /etc/init.d/.
> > 
> > I would generally agree, I'm presently setting up VM with a preinstalled
> > service in /opt running as its own user. When this service updates itself
> > it will only have access to the service location in /opt/<name> and
> > /srv/<name>, if I need to update the init script then I can do so in this
> > manner.
> 
> Is /opt mounted in a separate partition?
> 

Indeed, it is.

> Saludos
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://alioth-lists.debian.net/pipermail/pkg-systemd-maintainers/attachments/20160324/67d3271d/attachment-0002.html>


More information about the Pkg-systemd-maintainers mailing list