Background sessions now shut down cleanly when their terminal disappears.
What's wrong with this entry?
SIGHUP used to be ignored outright by background sessions. Now, if the process owns the controlling terminal, it records the signal and shuts down properly instead of lingering after the terminal goes away.
- Conditional on owning the controlling terminal; other background sessions still ignore SIGHUP.
- The shutdown is logged with the signal name and a flag noting the terminal ownership.
shutdown_signal", { signal: "SIGHUP", bg_ctty: !0 }
Strings lifted out of the shipped bundle, so the claim above can be checked against them.
Related
Other releases about the same thing. Found by shared names or similar wording; neither means one caused the other.
-
v2.1.234
Background task notifications arrive inside a system-reminder
Both mention background task
-
v2.1.235
Several finished background tasks now report as one line
Both mention background task
-
v2.1.236
Background-task notices no longer look like user approval
Both mention background task