geteilt von: https://sopuli.xyz/post/26841469
Meme transcription:
An obviously exhausted Spongebob is raising his arms in a rejoicing gesture. His face shows great tiredness, but also happiness.
Title: Finally finding your stupidity after hours of debugging.
I am days into trying to figure out how why systemd just won't start services after another service has successfully been run. I want service A to run, finish successfully and then service B to start. I've tries requires, wants, after and their reverse. I've tries paths with PathChanged and other things I've forgotten now. Either service B won't start because it's not WantedBy some target, but if I add that then it simply ignores the After, Requires, and Wants, and PathChanged to start anyway when the target has started.
It's maddening. Why are there so many conditions that express nearly the same thing but do so in such subtle ways that only testing will expose what it truly is, and sometimes not even that helps because obviously something else is missing but it won't say what. And AI of course has no fucking clue how to help.
Aaaaaaaaaaaaaaaaaah!
Anti Commercial-AI license
You’ve probably already found this answer on the Unix stack exchange, right? https://unix.stackexchange.com/questions/761630/how-can-i-make-a-systemd-service-start-after-the-completion-of-another-service
Yep! I've tried and it doest work. Either it's because I have mixed unit types (service mount service service and another case is service path service serviceX2), or I really just forgot something.
At this point I have to build a simplified version of my services with echo's and shit to be able to debug, because otherwise I'll just drop it and return whenever I find the motivation again.
Anti Commercial-AI license