Thraidh

This will be solved automatically by implementing #23.

Thanks for considering! Is there any way I can help?

When you spawn `sh -c 'sleep 60'` you are actually spawning a shell, that spawns a `sleep 60`. If you kill the shell using `kill`, `kill -9` or `process.destroy(..)` then...

I looked into this, but unfortunately it seems to be near impossible to implement this in `NuProcess`. `setsid` needs to be called between `fork` and `exec`, but that part is...

You can also write your own `setsid.pl` as ``` #!/usr/bin/perl use POSIX; POSIX::setsid(); exec @ARGV; ``` and run your command as `/path/to/setsid.pl originalcommand originalargs`. Then you don't need C or...

Just found that #66 and #67 would probably be fixed by changing `LinProcessFactory` to do what the documentation says. Also [the unit test](https://github.com/brettwooldridge/NuProcess/blob/master/src/test/java/com/zaxxer/nuprocess/CatTest.java#L201) should probably be fixed, too. Since the...

I'm not sure if this should be fixed, because it might break programs, that depend on `NuProcessBuilder.start` to never return `null`, even if the documentation says otherwise.

The correct way depends on the definition or view of "correct". Architecturally the best way would be to fix this as I wrote above. Unfortunately in the real world that...

I agree. `ProcessFactory` is obviously the wrong place. Apparently I rolled a natural one on Computer Science. I disagree about what the "correct" way is, though. The author has stated...

The problem is, that `NuProcessBuilder.start`'s documentation says, that it will return `null` on a failed start. OSX' and Linux' NuProcess implementations also support that, but `LinProcessFactory` is discarding that piece...