home *** CD-ROM | disk | FTP | other *** search
- Path: sparky!uunet!charon.amdahl.com!pacbell.com!decwrl!elroy.jpl.nasa.gov!sdd.hp.com!zaphod.mps.ohio-state.edu!uwm.edu!linac!att!bu.edu!cs!tasos
- From: tasos@cs.bu.edu (Anastasios Kotsikonas)
- Newsgroups: comp.unix.programmer
- Subject: Re: SO_REUSEADDR (was: Re: Socket Programming Help)
- Message-ID: <101017@bu.edu>
- Date: 8 Nov 92 19:04:42 GMT
- References: <1d9ihpINNep8@early-bird.think.com> <1992Nov7.023043.19007@wuecl.wustl.edu>
- Sender: news@bu.edu
- Organization: Computer Science Department, Boston University, Boston, MA, USA
- Lines: 15
-
- In article <1992Nov7.023043.19007@wuecl.wustl.edu> pete@arl.wustl.edu writes:
- >There is a discussion of this subject going on in comp.unix.internals. Someone there
- >had access to the source code, and in checking the coding of the SO_REUSEADDR
- >flag, determined that it doesn't work, which corresponded with my experiences in
- >attempting to use it as well. If anyone else has any insights into this problem of
- >closing sockets so that they can be immediately re-used, I'd be very interested
- >in hearing them.
- >
-
- I am sorry but this is nonsense. I have used SO_REUSEADDR on BSD 4.1.1, AIX
- 3.1.5 and up, HP UX 8.05 and up, SGI OS 4.0 and up and pure SVR4 systems,
- quite successfully I might add, for both privileged and non-privileged
- ports.
-
- Tasos
-