nodemon persists after terminal is closed

[sguillia]

• Versions: node@v14.3.0, linux@4.15.0-142-generic
• nodemon -v: 2.0.14
• Operating system/terminal environment (powershell, gitshell, etc): zsh
• Using Docker? What image:
• Command you ran:

# In terminal 1
touch empty-file.js
nodemon empty-file.js

# In terminal 2 (replace $PID by nodemon PID)
kill -HUP $PID

Expected behaviour

nodemon did exit

Actual behaviour

nodemon is still running

Steps to reproduce

See above

---

Any normal linux process is terminated when its terminal is closed. Except nodemon.

This project's readme advertises automatic restarting, but not SIGHUP immunity. Not knowing this leads to hard-to-debug issues like this one.

Is this behavior documented? Is there a rationale behind it? Is there a flag to disable it?
Thank you!

[remy]

nodemon uses the HUP signal to restart the sub process:

$ nodemon -V empty.js
[nodemon] 2.0.14
[nodemon] to restart at any time, enter `rs`
[nodemon] or send SIGHUP to 52589 to restart
[nodemon] watching path(s): *.*
[nodemon] watching extensions: js,mjs,json
[nodemon] starting `node empty.js`
[nodemon] forking
[nodemon] child pid: 52592

So when you send HUP to nodemon, it's handling the signal.

[Rinzwind]

For anyone else having this issue: further discussion is in issues #1667 and #1705.