Please don't use SIGKILL, USE SIGTERM

sigkill please

SIGKILL

mysql server crashes every 18 days, no oom, no crash logs, no sigkill being sent (used auditd). so I figure it's a unknown corner case bug in mysql. now I use a cron job to restart the damn thing every week at 3am, not a problem anymore

As a single guy literally trying to run a free service with 1.5M users I know one thing:

SIGKILL never fails.

I love software. Seriously, I love it. /s

Transmission is given a bad torrent (which, given that it's a torrent service, you'd expect it handles quite robustly) and completely fucks up. Like, really badly. It doesn't respond to RPC anymore, systemd has to resort to sending it a SIGKILL to get it off the process tree, and the web interface.. yeah. Nothing.

It doesn't log by default, so fine I'll add that to the systemd unit and restart it with debugging options enabled.

# systemctl daemon-reload && systemctl daemon-reexec

Turns out that /var/log/transmission.log can't be written to by my Transmission user. Well shit. Change that to /home/condor/transmission.log.

# systemctl daemon-reload && systemctl daemon-reexec
# systemctl restart transmission-daemon

*blood starts to reach its boiling point*

Still logs in the wrong fucking location. Systemd, I told you to log over there. I did everything I could to make you steaming pile of shit reload that fucking config. What's the fucking problem!?

*about 15 minutes of fighting systemd*
Finally! It spits out a log in the right location! Thank you Transmission and systemd for finally doing your fucking jobs. So a bad torrent it is, hmm...

*removes torrent from .config/transmission/torrents*
Transmission: *still fucking shits itself on that ostensibly removed torrent*

That's it. BEGONE!!!

Oh and don't get me started on the fact that apparently a service needs some 400MB of memory. Channeling your inner Chrome Transmission?

What do you think about the future of Visual Basic?

Oh boy, linux NFS bugs! this was supposed to be fixed in 2.x, but here I am, in kernel 6.1, same issue! `nfsiod` hangs, can't SIGKILL/SIGSEGV/SIGXCPU as root, `/proc/$pid/maps` is empty, strace/gdb are denied while running as root for only this process, `/proc/$pid/stack` only shows a single kthread that's stuck waiting for a fork to return, and... what the hell is `rescuer_thread`? apparently, deprecated in kernel 3.10, whatever the hell it is... wait, how did this even make a call without memory?

it's gonna be one of those days, isn't it?

When someone keeps on talking when they shouldn't, I always say SIGKILL. It's useful because everyone understands it or at least shuts up.

sigkill 2o2o

Cause when you die or exit from process it doesn’t matter how it happened, was it kill -9, sigkill or sigterm. As long as you go to hell / heaven / you name it and not to /dev/null you can still try to segfault the universe. Just give me the code !!!

And it aligns well with depression, alcoholism and lack of sleep.

Wish i could broadcast sigkill on to the subnet of idiots

REISUB.