Yo Hal!
On Mon, 21 Mar 2016 23:25:00 -0700
Hal Murray wrote:
> g...@rellim.com said:
> > Check out "man 7 signal", almost nothing is legal to call from
> > within a signal. You can't even open() of fopen() anything. About
> > the best you can do is write(STDERR,) and exit().
>
> Right. I
g...@rellim.com said:
> Check out "man 7 signal", almost nothing is legal to call from within a
> signal. You can't even open() of fopen() anything. About the best you can
> do is write(STDERR,) and exit().
Right. I was wondering if there was any software that would check that.
For ntpd, wri
Yo Hal!
On Mon, 21 Mar 2016 20:23:41 -0700
Hal Murray wrote:
> e...@thyrsus.com said:
> > I just ported in the Classic fix "[Bug 2814] msyslog deadlock when
> > signaled." I think that'll do it for this one.
>
> Is there any software that will check signal handlers to see if they
> call (or
e...@thyrsus.com said:
> I just ported in the Classic fix "[Bug 2814] msyslog deadlock when
> signaled." I think that'll do it for this one.
Is there any software that will check signal handlers to see if they call (or
call anything that calls) any non-signal-safe routines?
I don't know if it'
Hal Murray :
>
> A while (months) ago, we had troubles with msyslog scrambling output when
> called from the DNS thread and the main thread at the same time. That was
> fixed by adding a lock.
>
> That will deadlock if a signal handler calls msyslog when the signal goes off
> in the middle of
