On Mon, Feb 24, 2020 at 04:12:31PM +0300, innerspacepilot wrote:
> On 24.02.2020 13:23, Laurent Bercot wrote:
> > > SIGRTMIN+3 should also be caught and processed.
> >
> > What piece of software sends SIGRTMIN+3 to pid 1 when you're not
> > running systemd?
> >
> > --
> > Laurent
> >
>
On Sat, Dec 28, 2019 at 06:41:56PM +0100, Oliver Schad wrote:
> On Sat, 28 Dec 2019 15:37:35 +0200
> Alex Suykov wrote:
>
> > The reason I think it's mostly useless is because the only use case
> > for cgroup supervision is supervising double-forking daemons, which
> > is not a very smart thing
On Wed, Apr 01, 2020 at 05:13:06PM +, Laurent Bercot wrote:
>
> > There are pros and cons, but you are arguing for parsing stdout for a
> > text message and/or using pidfiles (written to an fd).
>
> I'm arguing for none of these things.
> I'm arguing for daemons to write a newline to a fd
On Fri, Apr 03, 2020 at 07:41:25AM +, Jonathan de Boyne Pollard wrote:
> Serge E. Hallyn:
>
> > If making changes to daemons were going to palatable, [...]
> >
>
> Clearly, it *is* palatable, given that a few people have been adding the
> systemd mechanism to
On Sat, Apr 04, 2020 at 09:29:04PM +, Laurent Bercot wrote:
>
> > Yes it sounds like I completely misread the earlier emails, sorry about
> > that. Now, looking at http://skarnet.org/software/s6/notifywhenup.html,
> > I'm probably not reading that quite right, but it seems to tie the
> >
I've been considering for several years trying to push a kernel patch
which would provide a way for userspace to find out when someone starts
listening on some port. Based on problems I saw long ago in the late
days of upstart and early days of systemd, that seemed like it would
solve a not
On Wed, Apr 01, 2020 at 03:06:49PM +, Laurent Bercot wrote:
> > I've been considering for several years trying to push a kernel patch
> > which would provide a way for userspace to find out when someone starts
> > listening on some port. Based on problems I saw long ago in the late
> > days
On Wed, Apr 01, 2020 at 03:59:25PM +, Laurent Bercot wrote:
> > You'd have to buy into it with a syscall that says "let me know when
> > something listens on tcp port N". In turn s6-supervise would only do
> > that if some config said "don't start service Y until something (which
> > is
