Process suspended when stdout and stderr are redirected and the process is daemonized

[vickychijwani]

Here's a shell session demonstrating the issue:

$ serve -s . >/dev/null 2>&1 &
[1] 31586
# after a couple of seconds, this message is displayed:
[1]  + 31586 suspended (tty output)  serve -s . > /dev/null 2>&1

# checking process status... output edited for readability
$ ps gv | grep serve
32623 pts/28   TNl    0:00      0 24425 898230 42720  0.2 node <some_path>/serve -s .

# the "T" in "TNl" above means the process is "stopped, either by a job control signal or because it is being traced."
# for details, go to https://linux.die.net/man/1/ps and Ctrl-F "process state codes"

# at this point, opening the link in the browser produces no response (connection stalls)

# however, all of these combinations work just fine:
$ serve -s . &                     # neither stdout nor stderr redirected
$ serve -s . >/dev/null &          # stderr not redirected
$ serve -s . 2>/dev/null &         # stdout not redirected
$ serve -s . 1>/dev/null 2>&1      # not backgrounded

As you can see, the issue only occurs if all 3 of the following conditions hold:

1. stdout is redirected (>/dev/null or 1>/dev/null)
2. stderr is redirected (2>/dev/null or, more commonly, 2>&1)
3. the process is sent to the background (trailing &)

[pablopunk]

This should be fixed once boxen uses a new binary for getting the window size.

See issue sindresorhus/terminal-size#3 (comment)

[pablopunk]

Updating the dependencies (npm install) should fix this but now although the process is not stopped immediately, it doesn't run the server (if you go to http://localhost:5000 it never loads)

[leo]

Already updated to the latest boxen!