Dominic Mitchell wrote: > On Tue, Aug 22, 2006 at 07:08:37PM -0500, [email protected] 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 */
You are being too kind to Linux' tardastic maze of include files. /usr/include/errno.h includes /usr/include/bits/errno.h includes /usr/include/linux/errno.h includes /usr/include/asm/errno.h includes /usr/include/asm-generic/errno.h, which seems to define most of the Econstants, but each of the headers seems to have bits and pieces of defines and undefines, some conditional and some not. Really, bits/errno.h, asm/errno.h? BITS? That's the lamest excuse for a naming convention evah. ASM? How did defining a few cpp constants become ASM? asm-generic is just adding insult to the insult.
