Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP Path: utzoo!watmath!clyde!burl!ulysses!mhuxl!ihnp4!zehntel!hplabs!sri-unix!dedwards@usc-isi From: dedwards%usc-isi@sri-unix.UUCP Newsgroups: net.unix-wizards Subject: Re: EOF with pipes. Message-ID: <17349@sri-arpa.UUCP> Date: Fri, 9-Mar-84 08:44:00 EST Article-I.D.: sri-arpa.17349 Posted: Fri Mar 9 08:44:00 1984 Date-Received: Tue, 13-Mar-84 08:06:40 EST Lines: 36 From: Howard S. WeissIt was done years ago on V6 at RAND - in fact here is a manual page: EOFP(II) 8-March-1977 EOFP(II) NAME eofp - write an end-of-file on a pipe SYNOPSIS eofp(fd); DESCRIPTION The pipe I/O routines have been modified to allow single end-of-files to be transmitted. It works as follows: a call to eofp guarantees that, after the real data is read, the next read on the pipe will return with 0 characters. Further writes may be done after writing an EOF, but they will be suspended until the EOF actually gets read. SEE ALSO pipe (II) BUGS Writing 0 characters on a pipe now has very special meaning--one's code should be checked to see that it disal- lows all writes of 0 characters unless really desired. -------