[Top][All Lists]

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

Re: lynx-dev Re: AIX Y2K upgrade problem

From: Clair Wilson
Subject: Re: lynx-dev Re: AIX Y2K upgrade problem
Date: Tue, 2 Feb 1999 11:22:15 -0500 (EST)


I found this on the web (for EBADF) :


          The accept call accepts a connection request from a remote
client and returns the socket number to be
          used for the session. 

                 int accept(int, struct sockaddr *, int *);

                 session = accept(listen,&sockaddr,&length);

                                The socket number assigned to the accepted
session is returned. Failure is
                                indicated by the return of -1. In this
case, check errno for the reason.
                                The socket number being used by a listen(
) call.
                                A pointer to a sockaddr structure or NULL.
If a pointer is provided, the address
                                of the accepted host is filled-in
                                A pointer to an integer that contains the
length of the sockaddr structure. This value
                                is required if sockaddr was specified. The
system will replace the original contents
                                of the length field with the filled-in
length of sockaddr.

          Return Codes

               If the accept( ) returns a value of -1, then the errno
variable will contain one of the following

     ============>   EBADF
                                     The listen parameter is not a valid
socket desc


So there we have it. EBADF means that the listen parameter is not valid.
But I have no idea how to fix that.

Thank You
Mr. Clair Wilson
Internet Administrator
Mainframe System Programmer
Information Services
Robert Packer Hospital
Sayre, Pa.


phone 717-882-5389
fax   717-882-5330

On Mon, 1 Feb 1999, Klaus Weide wrote:

> On Mon, 1 Feb 1999, Clair Wilson wrote:
> > Yes, all other products can get to the web. So that is not it.
> > The single / was a typo. It fails with http:// also.
> > So I am stumped. Thanks for your help. Any other ideas ?
> Try to find out which system call actually fails, and how.
> Try lynx -trace or ^T.
> If that doesn't give any clues, try something like strace, truss
> to trace system calls (don't know whether it exists for AIX).
>    Klaus

reply via email to

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