Try:
forstdin -d"\n" i s6-notifywhenup -f echo
with the latest execline git. That should be exactly what you need:
only one extra long-running process, no shell.
--
Laurent
pipeline -w { cd .. xargs -I{} s6-notifywhenup -f echo }
Except that I get a defunct echo process with and without the -f.
Ah, it must simply mean xargs doesn't wait on its children until the
next loop around.
--
Patrick Mahoney
On 2015-02-25 6:53 pm, Patrick Mahoney wrote:
On 2015-02-25 4:13 pm, Laurent Bercot wrote:
How about pipeline -w { cd .. forbacktickx -d"n" i { cat }
s6-notifywhenup -f echo } ... ?
This also works:
pipeline -w { cd .. xargs -I{} s6-notifywhenup -f echo }
Except that I get a defunct ec
On 2015-02-25 4:13 pm, Laurent Bercot wrote:
How about
pipeline -w
{
cd ..
forbacktickx -d"\n" i { cat } s6-notifywhenup -f echo
}
...
?
This is more elegant, thanks.
If you don't mind using a shell, you can even have a single shell
lying around instead of both a forbacktickx and a cat proc
On 26/02/2015 00:11, Olivier Brunel wrote:
Well, except that only the later will also create the "ready" file as
needed (i.e. w/ a TAI timestamp packed in it)...
Ah, indeed. s6-notifywhenup echo it is.
--
Laurent
On 02/25/15 23:13, Laurent Bercot wrote:
> (But really, "s6-ftrig-notify event U" is less hackish than
> "s6-notifywhenup echo".)
Well, except that only the later will also create the "ready" file as
needed (i.e. w/ a TAI timestamp packed in it)...
On 25/02/2015 22:29, Patrick Mahoney wrote:
The loopwhilex keeps the pump primed, so to speak, so /service/s can
be stopped and started many times with readiness reporting working.
Otherwise, I'd need to restart /service/s/log as well as /service/s.
On the other hand, I have mostly idle backtick
Hi Laurent,
Thanks for adding the readiness support to s6. Finally had a chance
to work with it a bit.
My current use case is upgrading a service on N host machines in
a rolling fashion, where the service is deployed to one machine,
restarted, and when it reports that it's ready, the process is
