Re: errno=104

[prev] [thread] [next] [lurker] [Date index for 2006/08/23]

On Tue, Aug 22, 2006 at 07:08:37PM -0500, mjinks@xxxxxxxx.xxx wrote:
> Cool.  Thanks, that's really helpful.  Somewhere along this chain of
> client<=>middleware<=>server, somebody encountered some difficulty and
> killed my connection.  Well thank goodness they threw an error!  An
> "errno=104"!  Now, I wonder who did the throwing?  And in what .h file
> buried deep in whoever's bowels might I find out what an "errno 104"
> FUCKING MEANS?

Normally, that's one of the standard Unix errno codes, which you should
be able to grep for.  It should be available in the include
<sys/errno.h> but that's too sensible for Linux.

    % egrep -w 104 /usr/include/**/errno.h
    /usr/include/asm-generic/errno.h:#define        ECONNRESET      104 /* Connection reset by peer */

Your're spot on about the message though, as there is a lovely
strerror(3) function for turning those error codes into nice human
readable strings.  You don't have to be a genius to find it.

-Dom

• errno=104 mjinks 01:08 on 23 Aug 2006
  • Re: errno=104 dom (Dominic Mitchell) 10:42 on 23 Aug 2006
    • Jarkko Hietaniemi 11:14 on 23 Aug 2006
    • Nik Clayton 11:32 on 23 Aug 2006
    • A. Pagaltzis 12:23 on 23 Aug 2006
      • too deep to show
    • Yossi Kreinin 18:08 on 26 Aug 2006
      • too deep to show
  • Michael Leuchtenburg 02:44 on 31 Aug 2006

Generated at 03:01 on 31 Aug 2006 by mariachi 0.52