Path: utzoo!utgpu!water!watmath!clyde!att!osu-cis!tut.cis.ohio-state.edu!mailrus!uwmcsd1!leah!itsgw!imagine!rpics!kyriazis
From: kyriazis@rpics (George Kyriazis)
Newsgroups: comp.unix.questions
Subject: Re: more unix jokes - /dev/null
Message-ID: <1255@imagine.PAWL.RPI.EDU>
Date: 26 Sep 88 03:36:41 GMT
References: <8488@smoke.ARPA> <26090@ucbvax.BERKELEY.EDU> <1049@sybase.sybase.com> <1414@star.cs.vu.nl> 
Sender: news@imagine.PAWL.RPI.EDU
Reply-To: kyriazis@turing.cs.rpi.edu (George Kyriazis)
Organization: RPI CS Dept.
Lines: 20

In article <7104@rpp386.Dallas.TX.US> jfh@rpp386.Dallas.TX.US (The Beach Bum) writes:
>In article <8572@smoke.ARPA> gwyn@brl.arpa (Doug Gwyn (VLD/VMB) ) writes:
>>In article <1247@imagine.PAWL.RPI.EDU> kyriazis@turing.cs.rpi.edu (George Kyriazis) writes:
>>>	command | vax
>>
>>No, the pipe will constipate since the "vax" command (equivalent to :)
>>does not read its input.
>
>No, the command will abort with SIGPIPE.  the vax command will exit,
>leaving no reader on the pipe.  the first time command goes to write
>to its stdout, a SIGPIPE will result...

I tried that command with 'ls' like 'ls | vax' and it worked; it gave
no output.  Nor it gave any error.



  George Kyriazis
  kyriazis@turing.cs.rpi.edu
------------------------------