On Fri, May 03, 2019 at 02:53:21AM +0200, Jeff wrote:
> > I have. The "rather artificial and constructed argument"
> > happened to me in real life, and it was a significant inconvenience.
>
> oh no, i hope it was not a remote server ... :-/
> always try things out on a box you have console access
El lun., 13 may. 2019 a las 18:09, Steve Litt escribió:
>
> […] not to sysvinit's
> comments-actually-mean-something five function essay length init
> scripts.
AFAIK, technically those are LSB-style init scripts, and have nothing
to do with sysvinit 'proper' (upstream sysvinit, that I believe Debi
El lun., 13 may. 2019 a las 14:14, multiplexd ()
escribió:
> It's been nearly two years since I set this up, so I don't recall all the
> details, but I started out with a sysvinit Debian 9 system, and
> reverse-engineered the boot sequence, which included a by-hand conversion
> of all
> the necess
On Mon, 13 May 2019 20:13:29 +0100
multiplexd wrote:
> All,
>
> On Fri, May 03, 2019 at 02:53:21AM +0200, Jeff wrote:
> > what init systems do this list's subscribers use ?
>
> I saw Guillermo's reply up-thread, so I thought I'd add my own two
> cents. My main workstation at present is a Debi
The signal used to request a configuration
reload from sysvinit is SIGUSR1 if I recall correctly
It must have been SIGHUP (at least in sysvinit-2.88dsf), which
reloads /etc/inittab. SIGUSR1 only closes and reopens /dev/initctl. :)
--
Laurent
All,
On Fri, May 03, 2019 at 02:53:21AM +0200, Jeff wrote:
> what init systems do this list's subscribers use ?
I saw Guillermo's reply up-thread, so I thought I'd add my own two cents. My
main workstation at present is a Debian 9 box booted with s6 and s6-rc, with
system setup and teardown (i.e.
