Re^3: Multiple system commands in parallel

I ran "help start" on Win XP. I presume that there are more options on other Window's O/S's. The "/B" option appears to do what you want? (ignore CTL-C?)

C:\>help start
Starts a separate window to run a specified program or command.

START ["title"] [/Dpath] [/I] [/MIN] [/MAX] [/SEPARATE | /SHARED]
      [/LOW | /NORMAL | /HIGH | /REALTIME | /ABOVENORMAL | /BELOWNORMA
+L]
      [/WAIT] [/B] [command/program]
      [parameters]

    "title"     Title to display in  window title bar.
    path        Starting directory
    B           Start application without creating a new window. The
                application has ^C handling ignored. Unless the applic
+ation
                enables ^C processing, ^Break is the only way to inter
+rupt
                the application
    I           The new environment will be the original environment p
+assed
                to the cmd.exe and not the current environment.
    MIN         Start window minimized
    MAX         Start window maximized
    SEPARATE    Start 16-bit Windows program in separate memory space
    SHARED      Start 16-bit Windows program in shared memory space
    LOW         Start application in the IDLE priority class
    NORMAL      Start application in the NORMAL priority class
    HIGH        Start application in the HIGH priority class
    REALTIME    Start application in the REALTIME priority class
    ABOVENORMAL Start application in the ABOVENORMAL priority class
    BELOWNORMAL Start application in the BELOWNORMAL priority class
    WAIT        Start application and wait for it to terminate
    command/program
                If it is an internal cmd command or a batch file then
                the command processor is run with the /K switch to cmd
+.exe.
                This means that the window will remain after the comma
+nd
                has been run.

                If it is not an internal cmd command or batch file the
+n
                it is a program and will run as either a windowed appl
+ication
                or a console application.

    parameters  These are the parameters passed to the command/program


If Command Extensions are enabled, external command invocation
through the command line or the START command changes as follows:

non-executable files may be invoked through their file association jus
+t
    by typing the name of the file as a command.  (e.g.  WORD.DOC woul
+d
    launch the application associated with the .DOC file extension).
    See the ASSOC and FTYPE commands for how to create these
    associations from within a command script.

When executing an application that is a 32-bit GUI application, CMD.EX
+E
    does not wait for the application to terminate before returning to
    the command prompt.  This new behavior does NOT occur if executing
    within a command script.

When executing a command line whose first token is the string "CMD "
    without an extension or path qualifier, then "CMD" is replaced wit
+h
    the value of the COMSPEC variable.  This prevents picking up CMD.E
+XE
    from the current directory.

When executing a command line whose first token does NOT contain an
    extension, then CMD.EXE uses the value of the PATHEXT
    environment variable to determine which extensions to look for
    and in what order.  The default value for the PATHEXT variable
    is:

        .COM;.EXE;.BAT;.CMD

    Notice the syntax is the same as the PATH variable, with
    semicolons separating the different elements.

When searching for an executable, if there is no match on any extensio
+n,
then looks to see if the name matches a directory name.  If it does, t
+he
START command launches the Explorer on that path.  If done from the
command line, it is the equivalent to doing a CD /D to that path.
C:\
[download]

Comment on Re^3: Multiple system commands in parallel Download Code

Replies are listed 'Best First'.
Re^4: Multiple system commands in parallel by BrowserUk (Patriarch) on May 10, 2016 at 00:51 UTC
The "/B" option appears to do what you want? (ignore CTL-C?) No. It doesn't: `C:\test>perl -e" system 'start /b c:/perl64/bin/perl.exe -E\"$^\|=1; sa +y ++$i while sleep 1\"'; sleep 1000" 1 2 3 4 5 Terminating on signal SIGINT(2) Terminating on signal SIGINT(2)` [download] That's both processes aborting. Contrast: `C:\test>perl -e" system 'start /min c:/perl64/bin/perl.exe -E\"$^\|=1; +say ++$i while sleep 1\"'; sleep 1000" Terminating on signal SIGINT(2)` [download] The initial process terminates, the second process continues to run, outputting to its own window. With the rise and rise of 'Social' network sites: 'Computers are making people easier to use everyday' 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". I knew I was on the right track :) In the absence of evidence, opinion is indistinguishable from prejudice.	[reply] [d/l] [select]

Replies are listed 'Best First'.

Re^4: Multiple system commands in parallel
by BrowserUk (Patriarch) on May 10, 2016 at 00:51 UTC

The "/B" option appears to do what you want? (ignore CTL-C?)

No. It doesn't:

C:\test>perl -e" system 'start /b c:/perl64/bin/perl.exe -E\"$^|=1; sa
+y ++$i while sleep 1\"'; sleep 1000"
1
2
3
4
5
Terminating on signal SIGINT(2)
Terminating on signal SIGINT(2)
[download]

That's both processes aborting.

Contrast:

C:\test>perl -e" system 'start /min c:/perl64/bin/perl.exe -E\"$^|=1; 
+say ++$i while sleep 1\"'; sleep 1000"
Terminating on signal SIGINT(2)
[download]

The initial process terminates, the second process continues to run, outputting to its own window.

With the rise and rise of 'Social' network sites: 'Computers are making people easier to use everyday'

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". I knew I was on the right track :)

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

[reply]
[d/l]
[select]