kill commands make one feel like a Caesar
et tu, Sudo?
Kill commands make me look like a CS:Go Civilian
one of my favourite things when i switched to linux first was using the meta+Q hotkey to shutdown a program (this was with PopOS i think). with windows there is alt+F4 but some programs only use shift+alt+F4 which makes it a lot more confusing. on top of all that if youre using a laptop then its another keypress for the Fn key in some cases
If your code can’t handle a sig9 then your code is weak
sig 9 or sig 9mm - that’s the question here
You literally kill/xkill/killall the program.
I’ve never seen anything graceful in windows
Windows: I refuse to shut down because of a, b , c
Me: But I already clos. . .
Windows: No you didnt’t, stop lying!
Me : Well, I pressed the X and the window dissappeared.
Windows: Lol, noob. Did you never even heard of a task managers?
“Mmm, that didn’t work, try again later I guess? Just stop bothering me with your petty needs and get back to generating monetizable data that I can harvest.”
Came here to say this. Windows goes full retard on everything it does. Graceful smh
Linux is actually great if you need to implement graceful shutdown with signals – I love it all around :)))
Laughs in Sierra
elaborate please
Linux does give every application time to shut down correctly, but unlike windows, it won’t wait for ages until every process is down. Linux WILL shut down in a certain timeframe, whereas windows waits for years if necessary. In my old job, we all had to use windows and I had times where I clicked shut down, turned off my monitor, grabbed my stuff, left and in the next morning, the PC was still on because Notepad refused to just close lmao.
That is what infuriates me so much. Instead of just killing the process after 5 mins of waiting it just cancels the shutdown. Like fuck off with that shit.
Depending on the use case, that can be a good thing or a bad thing
I don’t want my IDE with hours of work to just shut down forcibly.
Then you might not want windows cause Windows forces updates on you whether you want them or not and break things. Linux will happily wait for you to forget for so long it breaks because the target API doesn’t accept your old ass code anymore. At least in Linux as long as I don’t forget I’m good. I sometimes forget
TBF there are ways to completely disable updates in Windows (I just did in my VM because it should literally only run 3 programs which are not working with wine)
then surely you would not have asked your OS to shutdown? linux does what you ask
Shouldn’t be the default though.
Ha, you want choice in how your OS functions?
Here, have another bing toolbar for your settings app.Man I hope next time I press windows and type an application by name, or by executable.exe I get a spinning icon then a stack of unrelated web results that are probably malware.
I should probably sigterm instead of sigkill, but it sounds far less cool
If your app doesn’t respond to SIGTERM gracefully, you need to fix your app. The system did its job as documented.
$ kill -L 1) SIGHUP 2) SIGINT 3) SIGQUIT 4) SIGILL 5) SIGTRAP 6) SIGABRT 7) SIGBUS 8) SIGFPE 9) SIGKILL 10) SIGUSR1 11) SIGSEGV 12) SIGUSR2 13) SIGPIPE 14) SIGALRM 15) SIGTERM 16) SIGSTKFLT 17) SIGCHLD 18) SIGCONT 19) SIGSTOP 20) SIGTSTP 21) SIGTTIN 22) SIGTTOU 23) SIGURG 24) SIGXCPU 25) SIGXFSZ 26) SIGVTALRM 27) SIGPROF 28) SIGWINCH 29) SIGIO 30) SIGPWR 31) SIGSYS 34) SIGRTMIN 35) SIGRTMIN+1 36) SIGRTMIN+2 37) SIGRTMIN+3 38) SIGRTMIN+4 39) SIGRTMIN+5 40) SIGRTMIN+6 41) SIGRTMIN+7 42) SIGRTMIN+8 43) SIGRTMIN+9 44) SIGRTMIN+10 45) SIGRTMIN+11 46) SIGRTMIN+12 47) SIGRTMIN+13 48) SIGRTMIN+14 49) SIGRTMIN+15 50) SIGRTMAX-14 51) SIGRTMAX-13 52) SIGRTMAX-12 53) SIGRTMAX-11 54) SIGRTMAX-10 55) SIGRTMAX-9 56) SIGRTMAX-8 57) SIGRTMAX-7 58) SIGRTMAX-6 59) SIGRTMAX-5 60) SIGRTMAX-4 61) SIGRTMAX-3 62) SIGRTMAX-2 63) SIGRTMAX-1 64) SIGRTMAXSo does kill -4 just make the program a bit poorly?
It starts playing Beastie Boys over PC speaker
Only if you have installed the correct license file.
Unass my ram.
Linux gives processes a chance to gracefully close. However, it also will absolutely NOT allow a process to hang up the shutdown or restart procedure after a point. If you’re using systemd (which there is a good chance you are), it’ll count down. If the process hasn’t stopped in the time allotted, it gets Old Yellered.
When I use systemctl shutdown it happens instantly
If a process closes immediately from the shutdown command because it isn’t doing anything, sure.
Question, what’s the default wait time?
The default in systemd, unless your distribution has modified it either globally, or for a specific service, is 90 seconds
Depends on the process. Can be 30 seconds. Can be 5 minutes.
and this how I deleted the file I edited the entire day:
shutdown -h now. No go to bed NOW!Close correctly my ass, window’s priority is to piss us off.
I’ve tried to turn a pc off to go to sleep, only to realize in the morning it’s still on because some program refused to close.
Now when I see the prompt to force close, I just say yes.
