Re: __kernel_vsyscall () hangs in SIGCHLD handler

2007-09-26 Thread Mikael Pettersson
Ulrich Drepper writes: > On 9/26/07, John Z. Bohach <[EMAIL PROTECTED]> wrote: > > Is there some reason that syslog() sleeps in __kernel_vsyscall() when > > invoked from a signal handler? > > Only very few functions are allowed to be called from signal handlers. > This is clearly spelled ou

Re: __kernel_vsyscall () hangs in SIGCHLD handler

2007-09-26 Thread John Z. Bohach
On Wednesday 26 September 2007 10:03:33 Ulrich Drepper wrote: > On 9/26/07, John Z. Bohach <[EMAIL PROTECTED]> wrote: > > Is there some reason that syslog() sleeps in __kernel_vsyscall() > > when invoked from a signal handler? > > Only very few functions are allowed to be called from signal > handl

Re: __kernel_vsyscall () hangs in SIGCHLD handler

2007-09-26 Thread Ulrich Drepper
On 9/26/07, John Z. Bohach <[EMAIL PROTECTED]> wrote: > Is there some reason that syslog() sleeps in __kernel_vsyscall() when > invoked from a signal handler? Only very few functions are allowed to be called from signal handlers. This is clearly spelled out in the POSIX spec. Section XSH 2.4.3 l

__kernel_vsyscall () hangs in SIGCHLD handler

2007-09-26 Thread John Z. Bohach
Is there some reason that syslog() sleeps in __kernel_vsyscall() when invoked from a signal handler? Is it that I am not allowed to call any system calls from inside a signal handler? I use syslog() from a daemon client/server sys. app. that (tries) to log whenever a child exits. I've registe