-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 The Monday 2006-01-09 at 16:42 -0800, Jim Cunning wrote:
On Mon, 2006-01-09 at 15:16, Carlos E. R. wrote:
I went to "man read", and it says the only valid option is "-r", there is not "-t" option. This is in conflict on what "man bash" says for the "read" entry. Strange....on my 9.1 system, "man read" says:
read [-ers] [-u fd] [-t timeout] [-a aname] [-p prompt] [-n nchars] [-d delim] [name ...] One line is read from the standard input, or from the file descriptor fd supplied as an argument to the -u option, and the first word is assigned to the first name, the second word to the second name, and so on, with leftover words and their interven
It is indeed strange. I have: READ(P) POSIX Programmer's Manual NAME read - read a line from standard input SYNOPSIS read [-r] var... DESCRIPTION The read utility shall read a single line from standard input. ... IEEE/The Open Group 2003 READ(P) I notice now that it is showing read(p). If I specify "man 1 read", then I get: cer@nimrodel:~> man 1 read No manual entry for read in section 1 cer@nimrodel:~> whatis read read (1) [bashbuiltins] - bash built-in commands, see bash(1) read (2) - read from a file descriptor read (n) - Read from a channel read (1p) - read a line from standard input read (3p) - read from a file So the separate man page read(1) has dissapeared, it refers the reader to bash(1) instead, and then read(1p) might be obsolete. That must be why you are getting a different page than me. I have tried your piece of code, and I suppose I get the "wrong" result. Each time I do " echo hello >> fifo" I get: data is (hello) read again but it doesn't timeout and output a list of "read again". It must be considering the named pipe as a file. - -- Cheers, Carlos Robinson -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.0 (GNU/Linux) Comment: Made with pgp4pine 1.76 iD8DBQFDw5PFtTMYHG2NR9URAobBAKCOedNV7DIDPSHpAnf+tB2BbHfK0QCfetLH bvDWzowfZvT0PQahMTNrKKA= =WZd/ -----END PGP SIGNATURE-----