Meganuke

DO NOT MERGE YET!!!
> Which completely breaks the routing of stderr/stdout for that executable

Nope, stdout and stderr are unaffected by a fork - you must be experiencing some other issue. here's proof: 

    $ echo hello &
    hello
    [1] 2082

> since it comes in a multi-threaded way

Not sure if by "multi-threaded" you mean stdout+stderr or the application output, but in both cases that's wrong. Unless they do something like `for i in 1..10 ; do myServer & ; done`, then there will be no problems with the output streams. If they do have a for loop, it makes sense to me to request that they do something like this, which will just cause the normal stdout to be prefixed with `[worker 1]`, `[worker 2]`, etc

    for i in 1..10 
    do 
        myServer | sed "s/^/[worker $i] /" &
    done