04:10 <FromGitter> <skinnyjames> Is there a way to kill off a process and all of it's children given a PID? ⏎ sending `Signal::KILL` doesn't seem to do it.

04:21 <FromGitter> <naqvis> you need to send `SIGTERM` to kill process tree. So it should be `Signal::TERM` instead

04:35 <FromGitter> <skinnyjames> Ah, thanks!

04:40 <FromGitter> <skinnyjames> Would you also happen to know why: ⏎ ⏎ ```code paste, see link``` ⏎ ⏎ Won't pipe output from `test_server.rb` to `./some/log/file` from `Process.new` with shell as true, but does when I run it in a shell? [https://gitter.im/crystal-lang/crystal?at=63bb9ac23b37dd2c116e40b3]

05:06 <FromGitter> <naqvis> variables expansions is handled by SHELL, so don't believe you can have that variable expansion via the API

05:06 <FromGitter> <naqvis> you will have to perform the expansion yourself

05:06 <FromGitter> <naqvis> so instead of doing `${@}` you will have to provide the arguments when you perform `Process.new`

06:27 <FromGitter> <skinnyjames> Ah yeah, I think when I provide them as one string, it creates 2 processes (a shell and a ruby one). I can stop the returned PID with TERM/KILL/STOP, but it leaves a dangling ruby process

06:48 <FromGitter> <skinnyjames> Ah, i think I got it now. ⏎ ⏎ 1) it has to be one string ⏎ 2) piping output creates different processes in the same group ⏎ 3) Process.signal(Signal::STOP, -Process.pgid(pid)) appears to stop the group [https://gitter.im/crystal-lang/crystal?at=63bbb8bdbe2c3c20c73d8b68]