Bug#819040: insserv: Symlinked init script in /etc/init.d/ fails to be recognised on reboot.
> On 24 Mar 2016, at 08:04, Felipe Sateler wrote: > > (please don't top-post) > >> On 23 March 2016 at 18:02, Brett Ryan wrote: >> Interesting. Does that mean if /usr is mounted separately that it would also >> cause init to fail? > > Only if you do not use an initramfs. If you use a stock debian kernel > and initramfs, then you are alright. So how is /opt different if in the same order? > -- > > Saludos, > Felipe Sateler
Bug#819040: insserv: Symlinked init script in /etc/init.d/ fails to be recognised on reboot.
> On 23 Mar 2016, at 22:05, Felipe Sateler wrote: > > On Wed, 23 Mar 2016 18:52:20 +1100 Brett Ryan wrote: > > > > > On 23 Mar 2016, at 18:39, Petter Reinholdtsen 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/ and > > /srv/, 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
Bug#819040: insserv: Symlinked init script in /etc/init.d/ fails to be recognised on reboot.
> On 23 Mar 2016, at 18:39, Petter Reinholdtsen 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/ and /srv/, if I need to update the init script then I can do so in this manner.
Bug#819040: insserv: Symlinked init script in /etc/init.d/ fails to be recognised on reboot.
Package: insserv Version: 1.14.0-5 Severity: normal Dear Maintainer, If an init script is symlinked to /etc/init.d/ and a call is made to `update-rc.d' the init script will function correctly for the remainder of the uptime of that machine. Once the machine has restarted a call to start the service results in: Failed to start .service: .service failed to load: No such file or directory. This can be resolved by instead copying the init script and reissuing `update-rc.d'. -- System Information: Debian Release: 8.3 APT prefers stable-updates APT policy: (500, 'stable-updates'), (500, 'stable') Architecture: amd64 (x86_64) Kernel: Linux 3.16.0-4-amd64 (SMP w/2 CPU cores) Locale: LANG=en_AU.UTF-8, LC_CTYPE=en_AU.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) Versions of packages insserv depends on: ii libc6 2.19-18+deb8u3 insserv recommends no packages. Versions of packages insserv suggests: pn bootchart2 -- no debconf information
