cm0002@infosec.pub to Programmer Humor@programming.dev · 24 hours agoClosing programsinfosec.pubimagemessage-square117fedilinkarrow-up1639arrow-down186
arrow-up1553arrow-down1imageClosing programsinfosec.pubcm0002@infosec.pub to Programmer Humor@programming.dev · 24 hours agomessage-square117fedilink
minus-squareVogi@piefed.sociallinkfedilinkEnglisharrow-up55·23 hours agoIsn’t that what SIGTERM is? A request to gracefully shutdown processes.
minus-square9point6@lemmy.worldlinkfedilinkarrow-up23·22 hours agokill, and I swear to god if you’re still there when I ps, I’m getting out the -9
minus-square6️⃣9️⃣4️⃣2️⃣0️⃣@lemmy.worldlinkfedilinkEnglisharrow-up16·18 hours agoalias murder="kill -9"
minus-squaremarcos@lemmy.worldlinkfedilinkarrow-up9·21 hours agoYeah, by default kill sends sigterm, and not kill the process at all. It’s the correct behavior, sending sigkill by default would be harmful. Now take a look at how killall worked in Solaris (before it adopted GNU).
minus-squaretoynbee@lemmy.worldlinkfedilinkarrow-up3·21 hours agohttps://youtube.com/watch?v=Fow7iUaKrq4
minus-square9point6@lemmy.worldlinkfedilinkarrow-up2·12 hours agoOkay that took me by surprise I’ll be sharing this
minus-squarepewpew@feddit.itlinkfedilinkarrow-up13·23 hours agoSystemd waits until the services terminate before shutting down
minus-square[object Object]@lemmy.worldlinkfedilinkarrow-up1·14 hours agoI bet the GUI environments also have their own mechanisms to indicate that the app needs to close, before whipping out the signals.
minus-squarepivot_root@lemmy.worldlinkfedilinkarrow-up9·22 hours 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-up2·20 hours 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.
Isn’t that what
SIGTERMis? A request to gracefully shutdown processes.kill, and I swear to god if you’re still there when Ips, I’m getting out the-9Yeah, by default
killsends sigterm, and not kill the process at all.It’s the correct behavior, sending sigkill by default would be harmful. Now take a look at how
killallworked in Solaris (before it adopted GNU).https://youtube.com/watch?v=Fow7iUaKrq4
Okay that took me by surprise
I’ll be sharing this
Please do!
Systemd waits until the services terminate before shutting down
killall -9I bet the GUI environments also have their own mechanisms to indicate that the app needs to close, before whipping out the signals.
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.