Do you have a "killswitch" for when something on your system goes wrong? If so, expel the details about it. I got tired of windows freezing so I wrote something to kill the window, and the actual pid. Forcefully. I call it "rapenkill". I'm sure there are better ways to do what I'm doing but it just IS what it is right now.
I actually had to rewrite it because when writing the initial version I was retarded and did not consider "orphaned" processes. I think I used that terminology right? I don't know. Anyway, stuff like wineserver (which I kill via wineserver --kill).
I just wanted to get a new conversation going before I head to bed. I hope to wake up to replies. Goodnight /g/.
go back
>>109668561[your sage has been dispelled]If it's the Glegle images, do not fret. I can post frogs if you want. I just think they're funny but I realized I may have unintentionally avatarfagged. That was not my goal.
>>109668575nigger
I have two types of "when things go wrong": nvidia driver freezing the system, and OOM. the reset button on my pc case is the solution to either. driver freezes are impossible to anticipate and impossible to recover from. OOM freezes can be seen coming but you have to decide if you want to kill it and lose your progress, or gamble and see if the shitty linux memory system will free some memory before it completely fills.
>>109668476lol, on linux this is just 'kill -9 <pid>' or 'xkill', you basically reinvented the kill command for windows>killswitchThis usually refers to a hardware kill switch, you know, like an actual switch that powers off or disconnects your camera or bluetooth from the motherboard when you press it. What you're describing here is just killing processes which is not the same thing
>>109668495You should get a kys-switch
fuck off
