Re^2: Cannot print child process command during fork

If he did 24 system calls in a loop, wouldn't they all run serially rather than in parallel as now?

Examine what is said, not who speaks -- Silence betokens consent -- Love the truth but pardon error.

"Science is about questioning the status quo. Questioning authority".

In the absence of evidence, opinion is indistinguishable from prejudice.

"Too many [] have been sedated by an oppressive environment of political correctness and risk aversion."

Comment on Re^2: Cannot print child process command during fork

Replies are listed 'Best First'.
Re^3: Cannot print child process command during fork by NetWallah (Canon) on Aug 02, 2007 at 14:56 UTC
Since no useful work appears to be done at the conclusion of the forked child processes, and $proc and $cmd were unspecified, I assumed that $cmd was a brief command that started a remote process, and exited. If this is the case, the difference between serial and parallel processing would not be significant. So, point taken. I should have clarified my assumptions. "An undefined problem has an infinite number of solutions." - Robert A. Humphrey "If you're not part of the solution, you're part of the precipitate." - Henry J. Tillman	[reply]

Replies are listed 'Best First'.

Re^3: Cannot print child process command during fork
by NetWallah (Canon) on Aug 02, 2007 at 14:56 UTC

So, point taken. I should have clarified my assumptions.

"An undefined problem has an infinite number of solutions." - Robert A. Humphrey "If you're not part of the solution, you're part of the precipitate." - Henry J. Tillman

[reply]