▲ 641 ▼ Closing programs (infosec.pub) submitted 9 months ago by cm0002@infosec.pub to c/programmer_humor@programming.dev 129 comments fedilink hide all child comments
[–] cannedtuna@lemmy.world 0 points 9 months ago (2 children) How’s that differ from SIGHUP? permalink fedilink source parent hideshow 2 child comments replies: [–] pivot_root@lemmy.world 9 points 9 months ago Historical context, delivery, and handling. HUP—hang up—is sent to indicate the TTY is closed. TERM—terminate— is sent by request. What happens when received is usually up to the process. Most of them just leave the defaults, which is to exit. permalink fedilink source parent [–] firelizzard@programming.dev 3 points 9 months ago They’re different signals. The default handling is the same - terminate - but they’re triggered by different things and (if the process handles them) handled by separate handlers. permalink fedilink source parent
[–] pivot_root@lemmy.world 9 points 9 months ago Historical context, delivery, and handling. HUP—hang up—is sent to indicate the TTY is closed. TERM—terminate— is sent by request. What happens when received is usually up to the process. Most of them just leave the defaults, which is to exit. permalink fedilink source parent
[–] firelizzard@programming.dev 3 points 9 months ago They’re different signals. The default handling is the same - terminate - but they’re triggered by different things and (if the process handles them) handled by separate handlers. permalink fedilink source parent
