On Tue, 29 May 2001, Julius C. Duque wrote:
> On 28 May 2001, Thomas Rasmussen wrote:
>
> > >>>>> "Julius" == Julius C Duque <[EMAIL PROTECTED]> writes:
> >
> > Julius> Try grep-ing signal 11 from the Linux kernel source. This
> > Julius> error could be emitted by the kernel.
> >
> > Well I don't really see why grepping the source should change
> > anything... I've just grepped:
> >
> > % grep -ri "signal 11" * /usr/src/linux
>
>
> You did upgrade your kernel, right? If you have upgraded to
> Linux 2.4.3 (BTW, 2.4.5 is already out), get the source for
> 2.4.3 and find out what part of the kernel is giving out
> the error message. Also, you won't find an exact "signal 11"
> phrase. 11 is most probably #define-ed elsewhere.
I just did some checks. This signal 11 error is NOT from the
Linux kernel. It's from serverloop.c of openssh:
/* Check if the program terminated due to a signal. */
if (WIFSIGNALED(wait_status))
packet_disconnect("Command terminated on signal %d.",
WTERMSIG(wait_status));
Why this happens is still not clear to me, though. I'll dig deeper.
--
Under capitalism, man exploits man.
Under communism, it's just the opposite.
-- J.K. Galbraith
