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's possible to write real code following that rule. The case I'm thinking of is a trap handler that catches a fatal error and wants to print out a useful message and then exit somewhat cleanly. I think I'd be willing to handle the hard cases by hand, or with as much help as I can get. -- These are my opinions. I hate spam. _______________________________________________ devel mailing list devel@ntpsec.org http://lists.ntpsec.org/mailman/listinfo/devel