In local.freebsd.stable you write:
>Hello, people.
>The problem is - when doing execl() after fork() inside a signal handler,
>the signal is not delivered to executed child anymore. Is this correct? (I
>understand, that doing such things is a bad idea, but... :)
Looks like a result of the signal by default being blocked while the
signal handler is executing. The child inherits the signal mask.
Looks like linux (some version) behaves in the same way, but not
(random versions of) solaris, hp-ux and aix.
If you want to portably have full control over signal handling, you
have to do it yourself using sigprocmask(), sigaction() etc.
And yes, it is probably a bad idea to call things like syslog() in a
signal handler :^)
$.02,
/Mikko
--
Mikko Työläjä[EMAIL PROTECTED]
RSA Security
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-stable" in the body of the message
