Return to BSD News archive
Xref: sserve comp.unix.ultrix:17367 comp.unix.programmer:8926 comp.unix.bsd:11799
Newsgroups: comp.unix.ultrix,comp.unix.programmer,comp.unix.bsd
Path: sserve!newshost.anu.edu.au!munnari.oz.au!sgiblab!sdd.hp.com!nigel.msen.com!math.fu-berlin.de!ifmsun8.ifm.uni-hamburg.de!lutzifer!ccwnoc.hanse.de!jwminhh!wieck
From: wieck@jwminhh.hanse.de (Jan Wieck)
Subject: Re: Peculiar behavior of pclose() -- mistery solved (long)
Message-ID: <1993Apr12.114130.15968@jwminhh.hanse.de>
Organization: Private Site under Mach386
X-Newsreader: Tin 1.1 PL4
References: <1993Apr11.044800.6582@midway.uchicago.edu>
Date: Mon, 12 Apr 1993 11:41:30 GMT
Lines: 20
besp@ellis.uchicago.edu (Anna Pluzhnikov) writes:
: In article <PRZEMEK.93Mar28212112@rrdstrad.nist.gov> przemek@rrdstrad.nist.gov (Przemek Klosowski) writes:
: >
: >I came across a peculiar behavior of pclose(); when only one file is
: >popen()'ed, everything works as the man page and Stevens' book
: >claim: pclose() closes the pipe and kills the child process.
:
: pclose() doesn't kill the child, it just closes pipe to the child, so
: the child gets EOF and exits by itself.
Or gets SIGPIPE on the next attempt to write.
Until later, Jan
--
#===============================================#
# Mach 2.6 - Thats fast enough for my #
# private jet #
#========== wieck@jwminhh.hanse.de (Jan Wieck) =#