Re: fork() and file descriptors with un-flushed output

Thank you both! You learn something everyday. Thank you very much! The suggestions from Daniel worked beautifully! /Thomas 28 aug 2012 kl. 09:07 skrev "Wolf Geldmacher [via Cygwin]" : > This is not a bug - it's a feature ;-) > > The "issue" you are describing is in fact the standard behav

Re: fork() and file descriptors with un-flushed output

This is not a bug - it's a feature ;-) The "issue" you are describing is in fact the standard behaviour expected of fork() in any unix/posix compliant implementation. From the fork man page on Linux: ... fork() creates a new process by duplicating the calling process. The new process, re

Re: fork() and file descriptors with un-flushed output

On 8/27/2012 11:26 PM, thoni56 wrote: > Is this a known behaviour? Unavoidable in cygwin? (Obviously not, if I'm on > the right track with my guesswork...) If it is a bug, will it be fixed? This behavior isn't Cygwin-specific. In fact, it's longstanding Unix behavior. (The buffering problem is one