bleistift2

No-one said anything about sending the comment

Have you heard of !test_posts@reddthat.com or !test@lemmy.ml or !test@sh.itjust.works or !test@lemm.ee or !test@mander.xyz or !test@pabw.social?

Irgendwas machst du falsch. Ich drücke jeden Morgen Zement aus mir raus.

show you a GUI saying “you’re running low on memory, here are your running programs and how much they are using”

Good luck with this approach on a server.

If by ‘suspend’ you mean that the process will just halt, then: Which processes? All of them? Good luck displaying a message then. The last one that made a memory request? That might not be the true offender. The highest-consuming process? Same logic applies.

If by ‘suspend’ you mean moving the memory to disk, then a single misbehaving process, may end up eating all of memory and all remaining disk space.

The map even includes the oil spill in the Gulf of Mexico! I’ll take it.

Wait till you’re German and hear that name.

The customer knew the item would be defective and purchased anyway because they know they could refund it at no cost of their own. But as pointed out in our sibling thread, there are costs produced by refunds, which someone has to pay. Therefore the buyer made the choice to hurt these other parties. That’s where the moral comes in.

You know, !aneurysmposting@sopuli.xyz exists.

I did try to catch all of these signals:

                | "SIGABRT"
                | "SIGALRM"
                | "SIGBUS"
                | "SIGCHLD"
                | "SIGCONT"
                | "SIGFPE"
                | "SIGHUP"
                | "SIGILL"
                | "SIGINT"
                | "SIGIO"
                | "SIGIOT"
                | "SIGKILL"
                | "SIGPIPE"
                | "SIGPOLL"
                | "SIGPROF"
                | "SIGPWR"
                | "SIGQUIT"
                | "SIGSEGV"
                | "SIGSTKFLT"
                | "SIGSTOP"
                | "SIGSYS"
                | "SIGTERM"
                | "SIGTRAP"
                | "SIGTSTP"
                | "SIGTTIN"
                | "SIGTTOU"
                | "SIGUNUSED"
                | "SIGURG"
                | "SIGUSR1"
                | "SIGUSR2"
                | "SIGVTALRM"
                | "SIGWINCH"
                | "SIGXCPU"
                | "SIGXFSZ"
                | "SIGBREAK"
                | "SIGLOST"
                | "SIGINFO";

Sehr gerne, du Edwin.

You can’t know that from my issue description, but throwing a database at that problem really is ridiculous overkill.

Still thanks for the suggestion

When I run the script myself and kill it, it gets the signal and acts correctly. Only when I poweroff the system, this doesn’t work.

I also tried prepending exec, but no dice.