Hi James,
I have had a though, why not include symlinkable functionality for
halt, poweroff, shutdown, and reboot directly in s6-svscanctl
s6-svscan can be used as a normal process, not only as process 1,
and there can be more than one scan directory on the system.
Calling s6-svscanctl
On 03/01/2015 01:13, Avery Payne wrote:
I'm thinking spawn to background and exit just after that.
That solves the problem I mentioned, but creates other ones.
If ./finish is about cleanup, and you background it, then ./run
may start again before the cleanup has completed, so there will
be
.
Thanks,
Jim
Sent from my Windows Phone
From: Laurent Bercotmailto:ska-supervis...@skarnet.org
Sent: 1/2/2015 4:59 AM
To: supervision@list.skarnet.orgmailto:supervision@list.skarnet.org
Subject: Re: runit-scripts gone, supervision-scripts progress
Hi Avery
On Fri, Jan 2, 2015 at 3:42 PM, James Powell james4...@hotmail.com wrote:
Anyways, I'll be posting more frequently about getting init-stage-1/2/3
drafted correctly and in execline script language. Avery maybe you can
share your notes as well on this with me, if possible.
I'll provide what
One way or the other, ./finish should only be used scarcely, for clean-up
duties that absolutely need to happen when the long-lived process has died:
removing stale or temporary files, for instance. Those should be brief
operations and absolutely cannot block.
I'm thinking spawn to
