Skip site navigation (1)Skip section navigation (2)
Date:      Sun, 11 Feb 2001 11:39:51 -0800 (PST)
From:      Matt Dillon <dillon@earth.backplane.com>
To:        "Brandon S. Allbery KF8NH" <allbery@ece.cmu.edu>
Cc:        Barney Wolff <barney@pit.databus.com>, Blaz Zupan <blaz@amis.net>, Andrew.Hodgkins@hurlburt.af.mil, kstewart@urx.com, freebsd-stable@FreeBSD.ORG
Subject:   Re: RE: Proposed makewhatis perl script fix
Message-ID:  <200102111939.f1BJdpC33248@earth.backplane.com>
References:   <23180000.981905303@pyanfar.ece.cmu.edu>

next in thread | previous in thread | raw e-mail | index | archive | help
    From the signal() manual page:

     When a process which has installed signal handlers forks, the child pro-
     cess inherits the signals.  All caught signals may be reset to their de-
     fault action by a call to the execve(2) function; ignored signals remain
     ignored.

    So I would say that it is definitely ssh that is changing the SIGPIPE
    methodology.  gunzip must be exiting without generating an error message
    with SIGPIPE is SIG_DFL.  If gunzip were ever to catch the signal and
    report it, though, we will wind up with the errors popping up again,
    even if we fix ssh.  For now I think ssh should be fixed.

						-Matt


:On Sunday, February 11, 2001 03:41:48 -0500, Barney Wolff 
:<barney@pit.databus.com> wrote:
:+-----
:| Er, could it possibly be that telnet has been hiding the error
:| all along?  It's really, really hard to see how ssh could
:| *create* this sort of error.
:+--->8
:
:Someone mentioned earlier that sshd seemed to be setting SIGPIPE to SIG_IGN 
:in the child shell; that would lead to subprocesses getting EPIPE instead 
:of SIGPIPE, and typically the application reports the former and tar's 
:parent the latter, so the new error behavior would be expected.
:
:-- 
:brandon s. allbery     [os/2][linux][solaris][japh]   allbery@kf8nh.apk.net
:system administrator        [WAY too many hats]         allbery@ece.cmu.edu


To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-stable" in the body of the message




Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?200102111939.f1BJdpC33248>