Henning Meier-Geinitz schrieb am 16.07.05 22:09:14:
> Hi,
> On Fri, Jul 15, 2005 at 12:48:32PM +0200, Richard Metzger wrote:
> > Please, what is the design here? Shouldn't the child block the pipe,
> > so that the parent only returns from read(), when the child wants it
> > to?
>
> Parent: crea
Hi,
On Fri, Jul 15, 2005 at 12:48:32PM +0200, Richard Metzger wrote:
> Please, what is the design here? Shouldn't the child block the pipe,
> so that the parent only returns from read(), when the child wants it
> to?
Parent: create pipe, fork, close writing side of pipe, wait for data
fro
Hi,
On Thu, Jul 14, 2005 at 03:46:09PM +0200, Richard Metzger wrote:
> If one of you thinks it's worth to persue this old-fashioned
> environment (I'm using Linux since quite some time and dislike
> Wintendo, but for several reasons it has to be Win98 in this case
> here) I'd appreciate any kind o
OK - I sticked my nose a bit further into it...
It looks like the parent closes the pipe (because it returns from read() with 0
bytes read) before the child even has had the chance to supply anything into
the pipe.
-
[hp] do_read: Start readin
Hello great sane-team!
first of all - thanks to all you developers for all the sane code and to Frank
Zago for his Win-port.
Frank is right in one of his statements: "it may or may not work on
Win95/98/me"..
Well, meanwhile I know, that it doesn't work on Win 98 - because of missing
support f
