cm0002@infosec.pub to Programmer Humor@programming.dev · 8 个月前Closing programsinfosec.pubimagemessage-square149linkfedilinkarrow-up1787arrow-down1102
arrow-up1685arrow-down1imageClosing programsinfosec.pubcm0002@infosec.pub to Programmer Humor@programming.dev · 8 个月前message-square149linkfedilink
minus-squarevogi@piefed.sociallinkfedilinkEnglisharrow-up55·8 个月前Isn’t that what SIGTERM is? A request to gracefully shutdown processes.
minus-square9point6@lemmy.worldlinkfedilinkarrow-up25·8 个月前kill, and I swear to god if you’re still there when I ps, I’m getting out the -9
minus-squaremarcos@lemmy.worldlinkfedilinkarrow-up9·8 个月前Yeah, 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-square9point6@lemmy.worldlinkfedilinkarrow-up2·8 个月前Okay that took me by surprise I’ll be sharing this
minus-squarepewpew@feddit.itlinkfedilinkarrow-up13·8 个月前Systemd waits until the services terminate before shutting down
minus-squarepivot_root@lemmy.worldlinkfedilinkarrow-up10·8 个月前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.
minus-squareEthan@programming.devlinkfedilinkEnglisharrow-up3·8 个月前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.
minus-squarepet the cat, walk the dog@lemmy.worldlinkfedilinkarrow-up1·8 个月前I bet the GUI environments also have their own mechanisms to indicate that the app needs to close, before whipping out the signals.
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 -9How’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.
I bet the GUI environments also have their own mechanisms to indicate that the app needs to close, before whipping out the signals.