PS: EBADF means (E)rror: (Bad) (F)ile Descriptor
Most file I/O error flags start with E and have some kind of cryptic abbreviation next to it. That is, unless it is under Windows Sockets. Windows has it's own error code scheme. :) Just Google the net for the error code or error flag and you'll find all kinds of implementations and descriptions of the code. ------------------------------------------- Glen Batchelor IT Director All-Spec Industries phone: (910) 332-0424 fax: (910) 763-5664 e-mail: [EMAIL PROTECTED] ------------------------------------------- www.allspec.com ------------------------------------------- > -----Original Message----- > From: [EMAIL PROTECTED] [mailto:owner-u2- > [EMAIL PROTECTED] On Behalf Of [EMAIL PROTECTED] > Sent: Monday, February 20, 2006 12:19 PM > To: u2-users > Subject: [U2] Sockets API Message 29 > > I am running a special-purpose server using the Unidata 6.1 Sockets API. > Certain client timeout events cause me to receive Socket Error: > 29 SCK_EBADF. > > Interestingly, the Unidata 6.1 and 7.1 manuals give two different > descriptions: > > In Unidata 6 Manual: > b SCK_EBADF For Windows CE AF_IRDA sockets only: the shared serial port > is busyb > > In Unidata 7.1 Manual: > b SCK_EBADF Descriptor Socket is not valid.b > > Our environment is currently running Unidata 6.1. > > This server runs normally most of the time, and I'm trying to isolate the > client event that causes this condition. > > I haven't been able to find anything that describes this condition, and I > have only the fuzziest idea of what it means. > > Does anyone know what it means? Or point me to a reference that discusses > it in intelligible terms? > > Thanks so much in advance. > > Gizbolabobo > ------- > u2-users mailing list > [email protected] > To unsubscribe please visit http://listserver.u2ug.org/ ------- u2-users mailing list [email protected] To unsubscribe please visit http://listserver.u2ug.org/
