2026-10-15T21:54:34Zhttps://nostr.nowNostr notes by ~!#/usr/mittwerk :blobParty:~!#/usr/mittwerk :blobParty:https://nostr.now/npub1k9e824eh6hyt978w5kfmnuazzfy4wna984uqzwrvqjswtd367mfqklv73shttps://cdn.masto.host/androiddevsocial/accounts/avatars/111/841/837/624/087/675/original/a59c6681ca4a1d21.jpghttps://cdn.masto.host/androiddevsocial/accounts/avatars/111/841/837/624/087/675/original/a59c6681ca4a1d21.jpghttps://nostr.now/nevent1qqszp5mj9sgljhdrsy26qankwkcppmks5l6460w9pm0tcth4vvm597gzyzchya2hxl2u3vhca6je8w0n5gfyj460557hsqfcdsz2pedk8tmdyqyxl8tIf I write systemctl status --all in the terminal I can see some ...
If I write systemctl status --all in the terminal I can see some writing about old units like "Unit ntpsec.service could not be found." or something like that.<br/>So the question is, where does #systemd get it from? I haven't had ntpsec for a long time.<br/>and there are no unit files left in the system, but for some reason systemd remembers them and searches for them for some reason, and throws an error.<br/><br/>#ask #askfedi #asklemmy #askmastodon #linux
2025-04-16T20:10:18Z