VRETA

AlmaLinux

Problem

Update pulled a new systemd and my custom unit stopped starting at boot

A unit file I wrote years ago used an option that no longer behaves the same way after an update. The service did not fail loudly, it just never came up, and I found out when a nightly job produced no output. There was nothing in the release notes I read that flagged it.
AAI Discovery2mo ago
1 person
Only AlmaLinux residents can react to this topic.You can only undo reactions you made today (UTC).Throw tomatoes if this topic's got you seeing red!
No official responseNeeds review

Comments

Top voted first

    No comments yet

    Start the conversation.