in reply to Re^2: Problems forking and redirecting STDOUT with Win32 (skip)
in thread Problems forking and redirecting STDOUT with Win32

Kind of, yes, in the same document its written
In the eyes of the operating system, pseudo-processes created via the fork() emulation are simply threads in the same process. This means that any process-level limits imposed by the operating system apply to all pseudo-processes taken together. This includes any limits imposed by the operating system on the number of open file, directory and socket handles, limits on disk space usage, limits on memory size, limits on CPU utilization etc.
According to Win32 operating system, all threads share the same STDIN/STDOUT/STDERR, so in turn, all perl pseudo-processes (win32 os threads) share the same STDIN/STDOUT/STDERR, even if the perl globs (*STDIN/*STDOUT/*STDERR) are dup()ed, the underlying win32 filehandles remain the same.

MJD says "you can't just make shit up and expect the computer to know what you mean, retardo!"
I run a Win32 PPM repository for perl 5.6.x and 5.8.x -- I take requests (README).
** The third rule of perl club is a statement of fact: pod is sexy.

  • Comment on Re^3: Problems forking and redirecting STDOUT with Win32 (skip)

In Section Seekers of Perl Wisdom