home *** CD-ROM | disk | FTP | other *** search
- Path: sparky!uunet!elroy.jpl.nasa.gov!usc!rpi!bu.edu!cs!tasos
- From: tasos@cs.bu.edu (Anastasios Kotsikonas)
- Newsgroups: comp.unix.aix
- Subject: Re: prob w/ sockets
- Message-ID: <102769@bu.edu>
- Date: 21 Nov 92 15:52:51 GMT
- References: <102483@bu.edu> <1992Nov21.001323.16844@awdprime.austin.ibm.com>
- Sender: news@bu.edu
- Organization: Computer Science Department, Boston University, Boston, MA, USA
- Lines: 16
-
- In article <1992Nov21.001323.16844@awdprime.austin.ibm.com> peter@ski.austin.ibm.com (Peter Jeffe 512.838.4019) writes:
- >Actually, the relevant piece of code would be where you set the socket
- >to be non-blocking. Are you doing an ioctl(FIONBIO) or fcntl(SETFL,FNDELAY)?
- >If the latter, then you need to link with libbsd before libc to get the
- >bsd-style fcntl behavior (see /usr/lpp/bos/bsdport). If the former,
- >then I'm not sure what the problem could be, since non-blocking sockets
- >seems to work fine. Have you called the problem in to customer support?
-
- I am using fcntl and linking with -lbsd. Notice that the other socket *IS*
- behaving a non-blocking; it is the other one that's having the problem.
-
-
-
- Tasos
-
-
-