in reply to Re^3: Execute by order
in thread Execute by order

On *NIX, I submit it is easy to modify the command strings to run a command in parallel ... which, IIRC, isn't possible on Windoze.

How would you do it on *nix?

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.
RIP PCW It is as I've been saying!(Audio until 20090817)

Replies are listed 'Best First'.
Re^5: Execute by order
by Bloodnok (Vicar) on Aug 13, 2009 at 13:54 UTC
    ...at its simplest, by changing command to command &.

    However, by just doing the above, the backgrounded command will suspend if it needs to write to either device 1 or device 2 (STDOUT/STDERR in perl parlance), or read from device 0 (STDIN), so command is usually rewritten as command >file 2>&1 & to send all output from stdout and stderr to file.

    If you don't care about output from either stdout or stderr, the frequently seen idiom - command >/dev/null 2>&1 & - is used.

    A user level that continues to overstate my experience :-))
[reply]
[d/l]
[select]
      ...at its simplest, by changing command>/c> to <c>command &

      The equivalents on Win* are:

      1. start command
      2. start command > file 2>&1
      3. start command > nul  2>&1
      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.
[reply]
[d/l]
[select]
        TFT BrowserUk ,

        start looks familiar, but the *NIX-like re-direction syntax ? Is it/has it been recently introduced ?

        A user level that continues to overstate my experience :-))
[reply]
[d/l]

In Section Seekers of Perl Wisdom