cm0002@infosec.pub to Programmer Humor@programming.dev · 1 month agoClosing programsinfosec.pubimagemessage-square150linkfedilinkarrow-up1785arrow-down1101
arrow-up1684arrow-down1imageClosing programsinfosec.pubcm0002@infosec.pub to Programmer Humor@programming.dev · 1 month agomessage-square150linkfedilink
minus-squarecannedtuna@lemmy.worldlinkfedilinkarrow-up2arrow-down1·1 month agoHow’s that differ from SIGHUP?
minus-squarepivot_root@lemmy.worldlinkfedilinkarrow-up10·1 month agoHistorical 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.
minus-squareEthan@programming.devlinkfedilinkEnglisharrow-up3·1 month agoThey’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.
How’s that differ from
SIGHUP?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.
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.