[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [bug-inetutils] already connected when closed

From: Alfred M. Szmidt
Subject: Re: [bug-inetutils] already connected when closed
Date: Wed, 11 Jul 2007 20:35:04 +0200 (CEST)

   I can't explain why it doesn't happen on other hosts (especially
   with the exact same libc and kernel), but it doesn't actually seem
   like unreasonable behavior: the socket times out, and this is only
   detected at the fflush because that's when data is actually
   attempted to be written.  According to the `Sending Data' node in
   libc.info, SIGPIPE is to be expected.

As you say, it isn't unreasonable, but the funky thing is that it
actually happens.  I cannot recall ever seeing this reported, even
anything similar, and this code is age old.  Hey, could you maybe (it
isn't all that important, so if you are busy with more important stuff
please just ignore this idea) try and use the original BSD ftp?
Though, that might change things so much, that there won't be a
timeout.  Sighs.

   I notice that ftp sets a SIGPIPE handler in some other cases, so I tried
     signal (SIGPIPE, lostpeer);

Try doing this (somewhere) instead: signal (SIGPIPE, SIG_IGN);

reply via email to

[Prev in Thread] Current Thread [Next in Thread]