errno=104

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

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?

Sequel: as it happens, client and server in this case are both part of
the same package, so it seemed like a reasonable guess to go pawing
around in that package's headers.  Yay, 53 of them define something as
a "104", and of those 53 header files, none has a name with "err"
anywhere in it.  Lovely.  This of course assumes that the numbers in the
headers and the numbers reported at runtime are even in the same base,
such that my naive text string search is even vaguely on the right
track.

I mean honestly, numeric error codes, why the hell bother?  Why not just
die and keep your trap firmly shut so I'll know right away that I'm
going to be running two or three different processes inside debuggers,
rather than pretending to try to be informative?  Oh wait, I get it.
Never mind.

Loathe,
-j

• errno=104 mjinks 01:08 on 23 Aug 2006
  • Re: errno=104 dom (Dominic Mitchell) 10:42 on 23 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