home *** CD-ROM | disk | FTP | other *** search
- Path: sparky!uunet!zaphod.mps.ohio-state.edu!saimiri.primate.wisc.edu!sdd.hp.com!usc!elroy.jpl.nasa.gov!ames!agate!e260-1c.berkeley.edu!c60b-1fk
- From: c60b-1fk@e260-1c.berkeley.edu (Ahmon Dancy)
- Newsgroups: comp.os.linux
- Subject: select()
- Date: 17 Dec 1992 03:59:01 GMT
- Organization: University of California, Berkeley
- Lines: 21
- Distribution: world
- Message-ID: <1gotu5INN77h@agate.berkeley.edu>
- NNTP-Posting-Host: e260-1c.berkeley.edu
- Originator: c60b-1fk@e260-1c.berkeley.edu
-
-
- I don't know if this has been addressed before so I'll mention it.
- Here's the situation. I have some code like this:
-
- select(sock+1, &r, NULL, NULL, NULL);
- r is set for stdin and sock.
-
- The problem is that lets say 'sock' is continually ready to send,
- then the program will proceed like normal (printing what was received
- at sock). But if I hit SPACE on the keyboard, all input from sock
- stops and select doesn't report any more ready data until I hit
- return on the keyboard. Can anyone explain this? Is it supposed
- to be this way? I don't think so. It's kind of a nice feature for
- muds but it's easy for it get annoying. Do I need to do some ioctl on
- stdin?
-
- Any info is appreciated
- --
- -------------------------------------------------------------------------------
- Ahmon Dancy (c60b-1fk@webworm.berkeley.edu)
- -------------------------------------------------------------------------------
-