Remy Sharp

That's correct. nodemon sends the SIGUSR2 signal to the subprocess and if it doesn't exit within a predefined time frame, it'll force quit the sub process. Otherwise your sub process...

🤔 thinking back, I originally wrote it so that if you trapped the signal from nodemon then your script would be responsible for stopping. Logic has changed over the 11...

And with it comments out and *without* the sub process handling the exit itself does the spawned sub process still restart? In theory, the kill signal is still `SIGUSR2` which...

Sorry, I wasn't clear at all (!). If you remove the hook in your subprocess that listens for `SIGUSR2` does the process still restart?

Right, well first of all: excellent job in following up and digging. That's definitely a regression and I'll see if I can find time this week to sort it (or...

The issue raised on #1667 wasn't entirely clear on what the problem was, but this explanation has given me a lot more context, so for starters: thank you. On pass...

I'm trying to get my head fully around the problem this is trying to address - but it seems that it is either: about the signal forwarding from nodemon to...

So… Firstly, there's no real reason to justify changing the `rs` to `rl` particularly as it's in common usage. The design of my software is driven by ease of use...

I've also documented the current state of nodemon and how signals are handled when sent both to nodemon and to the subprocess: https://docs.google.com/spreadsheets/d/1gFxwZqv1cBPJpiqeVtYh0MIC30RJlx6g0VF-2B8pQDE/edit?usp=sharing

This doesn't cover the common case where the subprocess of nodemon then spawns it's own processes (with `concurrently` for for instance), but I would image the signal handling is up...