this post was submitted on 25 Dec 2024
365 points (99.5% liked)

Programmer Humor

19817 readers
993 users here now

Welcome to Programmer Humor!

This is a place where you can post jokes, memes, humor, etc. related to programming!

For sharing awful code theres also Programming Horror.

Rules

founded 2 years ago
MODERATORS
 
you are viewing a single comment's thread
view the rest of the comments
[–] [email protected] 7 points 1 day ago* (last edited 1 day ago) (5 children)

How are you running your script?

(I have no idea how to solve your issue I'm just asking questions to sound smart and helpful)

[–] [email protected] 7 points 1 day ago (4 children)

It’s a node process invoked by a run.sh, which gets executed via a .desktop file in the ~/.config/autostart directory.

I went with a systemd unit now and it works.

[–] [email protected] 7 points 1 day ago* (last edited 1 day ago) (1 children)

I can't remember off the top of my head, but your shell script might not be relaying the SIGTERM. Make sure you start your node process with the "exec" statement. This will replace the script's process with node instead of having node be a subprocess of your script.

[–] [email protected] 3 points 1 day ago

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.

load more comments (2 replies)
load more comments (2 replies)