Article View: comp.unix
Article #506Re: Pipes Signals Interprocess-I/O
From: Julian Elischer
Date: Fri, 15 Jan 1988 21:46
Date: Fri, 15 Jan 1988 21:46
20 lines
1438 bytes
1438 bytes
In article <2951@mcdchg.UUCP>, lanzo%mercutio@steinmetz.UUCP (Mark Lanzo) writes:
> I'm working on an application where I have a process fork off a 2nd process
lines deleted
> The problem that I am running into is that I need to be able to detect when
> the child process writes to the pipe; and I need the I/O to be as unbuffered
> as possible. I need the ability to detect writes asynchronously as well as
> synchronously.
I may be wrong, but I think that I recently read that doing a STAT
sometimes gives you the number of chars waiting in a pipe.
you will have to check yourself but it might solve th problem
If you're still waiting.. others might comment on this
as I can think of uses for this myself and cannot find reference to this
any more.
p.s. sorry for the late response but our feed has been down for 3 weeks
PLUS always allow 1 week for news in W. Australia.
julian elischer
UUCP: {lots of places,uunet,mcvax}!munnari!acp.oz!julian
ACSNET: julian@acp.oz
Technical Details
Message-ID:
<3452@mcdchg.UUCP>Path:
arc1-ca.pugleaf.net!utzoo!utgpu!water!watmath!clyde!mcdchg!usenetReferences:
<2951@mcdchg.UUCP>Show Full Headers
Complete Article Headers
Path: arc1-ca.pugleaf.net!utzoo!utgpu!water!watmath!clyde!mcdchg!usenet From: julian@acp.OZ (Julian Elischer) Newsgroups: comp.unix Subject: Re: Pipes Signals Interprocess-I/O Summary: In some systems STAT returns # chars in pipe Message-ID: <3452@mcdchg.UUCP> Date: 15 Jan 88 21:46:01 GMT References: <2951@mcdchg.UUCP> Sender: usenet@mcdchg.UUCP Organization: Australian Computer Products, Perth, Australia Lines: 20 Approved: usenet@mcdchg.UUCP