kill commands make one feel like a Caesar
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.
Laughs in Sierra
I’ve never seen anything graceful in windows
“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 :)))
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
Shouldn’t be the default though.
Ha, you want choice in how your OS functions?
Here, have another bing toolbar for your settings app.
I should probably sigterm instead of sigkill, but it sounds far less cool
Unass my ram.
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.
and this how I deleted the file I edited the entire day:
shutdown -h now. No go to bed NOW!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.
KILL KILL KILL
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.
-
Linux normally does a nice shutdown as well, unless you force it.
-
You can force it on windows if you really want.
I’m so tired of linux memes posted/made by people who don’t know much about windows or linux.
Oh, p-lease, can force it my ass, Linux has never failed to shutdown on me when using plain obvious GUI method. windows - can easily hang on forever as long as computer stays powered. The point of all the memes is exactly insane windows defaults, not the things that can or can’t be done by someone with enough knowledge
-
Linux programs either HAVE to be quick while receiving shutdown signal, otherwise the state will be fucked, work will be lost, and people will be mad, and program will stop being used.
-
Clicking the Windows button to force shutdown will straight up kill the program and won’t care at all.
-
Absolutely, if people agree or not, the core windows is still a pretty powerful operating system. Its sad that they are ruining it by adding crap into it.
I’m waiting for pure GNU/NT. It sure as hell ain’t Unix!
You can force it on windows if you really want.
Please elaborate
Theres a button on the back of the psu that comes in handy a LOT with windows. Useless on linux unless you want to use that button for its intended purpose.
Back in the day if I wanted to quit Windows the fastest way, I’d rename the c:/windows folder…
Back to the DOS prompt faster than you could blink
Shutdown.exe -r -t 00 -f
Fast , no mucking around with graceful exiting of stuff. Kicks it in the teefs
Some clarification of the command
-r #restart
-s #shutdown
-t 00 #wait 0 seconds
-f #forced
I use that as a bat file so all I have to do is double click it.
and then you can growl menacingly and say ‘don’t make me get the bat, punk’
I don’t use windows.
Not sure if this is a joke or serious.
I can’t speak for them if they’re joking or not but it’s something you can absolutely do. *.bat files (short for “batch”, as in a batch of commands to execute in sequence) are the script files for the Windows command line, and can be executed by double clicking on them
Thanks, I’m familiar with batch files. This just seems like a very bad way to perform a shutdown, especially when running a UI Desktop windowing system. And even if that shutdown command is fully supported from the GUI, I would guess you need to be admin to run it, which means you can run the bat file as admin, so if you can edit the file or modify the env in which it runs (e.g. PATH) it seems like it could be a security problem. And if you don’t need to be root to run the shutdown command, that seems like its own problem. I suppose Windows still has the “run as administrator” from the context menu so maybe that helps.
You did say “I don’t use Windows” which sounded like you were saying you didn’t know if what they were saying was technically plausible or reasonable, and without knowing what you do or don’t know about Windows or DOS, figured I’d respond with the presumption that it’s possible you’re only really familiar with *NIX systems (which is not a judgement).
I find it kludgey and unnecessary to shut down that way, but it’s not exactly a bad idea, and it does not require admin rights.
And there’s no reason it wouldn’t be supported: when you run the file, it opens it in a terminal window, it’s exactly like if you manually opened it and typed it from a technical point of view.
And if someone malicious has the ability to edit a file on your desktop, they could do a lot more dangerous things, pretty much anything you could put in the batch file, more or less directly.
Really, the only issue here is that you’d always be force closing your programs when you shut down which increases the odds that eventually they might corrupt one of their files… Not a huge risk, but non-zero.
As it is a simple command you don’t need to be an admin or run as administrator. Listen kids don’t run batch files if you don’t know where they came from or who made them.
00?
I know! I wasn’t sure when I posted it, so stuck to memory to be safe.
I reckon I’ve confused the double digits needed for the silly shutdown explanation thing (planned/unplanned, various reasons) instead…
lol, I honestly just thought the elite hackers used double zeros and I was just a lazy dummy. Maybe I’m the elite hacker then.
How many seconds you’re prepared to wait for Windows to shutdown.
Yeah, but why 00 and not 00000? Or 0.000?
Because that’s how they do it for Gundams
Probably just habit on their part, it’s no different than just putting 0
deleted by creator
I’ve used a single zero and that works fine too.
Me to
I will just do the update first /s
If -t is specified -f is assumed and redundant, but also it will try to do graceful l, but with a patience of a cranky toddler
Not really. If -f (force) is removed windows will shutdown similar to pressing the shutdown button and will wait for your input regarding open programs. -f is needed to just just “do it” with no hesitation or response from the user.
Straight from the doc
/t <xxx> Sets the time-out period before shutdown to xxx seconds. The valid range is 0-315360000 (10 years), with a default of 30. If the timeout period is greater than 0, the /f parameter is implied.
Sooo when you use the prompt
Shutdown.exe -r -t 00
You would need the -f since we defined the timeout period as 0. Because:
If the timeout period is greater than 0, the /f parameter is implied.
Yeah fair enough -f -s does the same thing as -t 0?
Ah nice. I have only used it with -t 0. I’m glad to have learn something today.
The process manager lets you kill any process.
You can also click the do it anyway button when it’s waiting on shutdown, but I’ve had less consistent success with that.
There’s also a hardware way, works on practically any device. Phone, tablet, laptop, desktop, etc. Doesn’t matter what the OS is.
Press and hold power button for anywhere between 5 - 15 seconds. The second half of this meme describes this method the best, methinks.
It was simpler using Linux to just kill things unceremoniously, but my coworkers are also consistently amazed when Epic throws a temper tantrum (rare, but it happens) and I walk over and ctrl-alt-delete and tell it to sit down and shut the fuck up until it’s ready to reboot and act right.
Epic?
I’m assuming Epic as in the healthcare charting system
☝️
deleted by creator
At the workplace?
-
