home *** CD-ROM | disk | FTP | other *** search
- Newsgroups: comp.os.linux
- Path: sparky!uunet!munnari.oz.au!bruce.cs.monash.edu.au!monu6!dibbler.cs.monash.edu.au!tym
- From: tym@dibbler.cs.monash.edu.au (Tim MacKenzie)
- Subject: Re: [Q] Bug in select(2)?
- Message-ID: <1992Dec18.144831.10900@monu6.cc.monash.edu.au>
- Sender: news@monu6.cc.monash.edu.au (Usenet system)
- Organization: Computer Science, Monash University, Australia
- X-Newsreader: TIN [version 1.1 PL8]
- References: <1992Dec16.082553.8574@mintaka.lcs.mit.edu>
- Date: Fri, 18 Dec 1992 14:48:31 GMT
- Lines: 43
-
- The Wyvern (wyvern@gnu.ai.mit.edu) wrote:
- >I've also been noticing some strange behavior which seems to be also due to
- >select(2), although it doesn't seem to be of the same type as mentioned
- >above. I'm running a client/server program that uses sockets of type AF_INET.
- >Up until 0.99 I wasn't having problems but now clients and servers are getting
- >stuck. They just hang. ps -l shows the WCHAN for the hung processes as
- >tcp_read
- >when normally it shows do_select when they're working correctly. The programs
-
- The way in which the tcp code does select has been changed recently.... I would
- recommend getting the latest tcp and testing your code with that. The current
- version (which is working well for me at the moment, except for asyncronous
- connect's which can be fixed with a simple patch) is 0.99pl0 p5. This is
- available in tsx-11.mit.edu:pub/linux/packages/tcpip/tcp99pl0-p5.Z
-
- This patch is for 0.99 plain. You do not need 0.99pl0 patches 1-4.
- I've tacked on Ross's tcp99pl0-p5.README
- --
- -Tim MacKenzie (tym@dibbler.cs.monash.edu.au)
-
- --- BEGIN included text tcp99pl0-p5.README
- Since some people had problems with patch4, this patch is off of the
- stock .99 sources. DO NOT apply patches 1-4 first. I won't be able
- to work on this for quite a while, so this is the last patch. In the
- interim I suggest those of you who find problems, figure out how to do
- a good bug report. "The daemons don't work," doesn't cut it. If you
- have a problem I need to know precisesly what it is including a syslog
- if possible. If the kernel prints out a message I need to know
- exactly what it said including any numbers it happend to print out. I
- also need to know how any addresses relate to YOUR system.map. Line
- numbers would help. Furthermore if something returns an error you
- don't think it should, I need to know preciesly what error (including
- the value of errno) and under what circumstances it occured and why it
- shouldn't return an error. Small programs to demonstrate things you
- consider bugs would help. The tcp/ip code has function almost
- flawlessly and continuosly for me since the Pre-Alpha days. Obviously
- I can't reproduce problems like ftp doesn't work and I will tend to
- ignore them.
-
- Ross Biro bir7@leland.stanford.edu
- Member League for Programming Freedom (LPF)
- mail lpf@uunet.uu.net to protect your Freedom
-
-