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

2016-03-23 Thread Felipe Sateler
On 23 March 2016 at 18:18, Brett Ryan wrote: > > >> 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? >> >> On

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

2016-03-23 Thread Brett Ryan
> 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

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

2016-03-23 Thread Felipe Sateler
(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. -- Saludos, Fel

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

2016-03-23 Thread Brett Ryan
> 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/. > > > >

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

2016-03-23 Thread Felipe Sateler
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 >

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

2016-03-23 Thread Brett Ryan
> 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

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

2016-03-23 Thread Petter Reinholdtsen
Control: reassign -1 systemd [Brett Ryan] > 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'. Th

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

2016-03-23 Thread Brett Ryan
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 serv