I generally am in the ambivalent-to-in-favor-of-systemd camp, i think it's a heck of a lot nicer than the randomass init scripts we used to have to deal with, but.....
Ha. Turns out my incoherent rant about #systemd actually got a response from Lennart Poettering, which I didn't see because he's on mastodon.social.
not that it helped because he went all "that's not a systemd issue"
(sure it isn't but as I mentioned I actually solved the issue with the variables. The issue now is that the stuff still doesn't actually start because... what was it this time? It closed with an exit code? The reset counter is too high? Or something about the wrong folder?)
finally have my #irc server running about the way I want. next thing will be linking it up to another server to create a tiny little irc network.
it really isn't hard to set up either this ircd (ngircd) or one of the alternatives in debian, the only thing I have issues with is how it interacts with #systemd when you try to restart it. but that's a systemd thing. and maybe I'm just bad at that.
otherwise you can just install the package and have a working irc server just like that.
replaced the #irc daemon I have running on my small machine with ngircd, which turns out to be much easier to configure than inspircd, and then stopped working once I tried to restart the service. #systemd man, I just can't...
#systemd v256~rc1 is out! You know the drill, download it, run it, find all the bugs and report them - possibly to somebody else, I'll be at the nearest pub
debugging between podman's container / quadlet file with systemd is kinda tricky, especially when there is a typo in the container file, there is not warning or error i can find from journalctl. took me a whole day + night to realized that 1 single typo. the parser is just too graceful... #podman#systemd
Freedesktop has a specification for idle inhibition[1] (which hinders sleep from triggering when you're watching videos, for example) exposed via org.freedesktop.ScreenSaver.Inhibit. To use it in your application, all you need to do is make a D-Bus call, whether it is Inhibit to enable it or UnInhibit to disable it.
The systemd suite includes a tool called systemd-inhibit[2] that lets you call some software and ensure that it will inhibit idle/poweroff/restart/reboot/suspend/hibernate for the duration of the software's lifetime. This is also exposed via org.freedesktop.login1.Manager.Inhibit!
KDE CLI tools includes a similar small utility called kde-inhibit[3] which in addition to supporting inhibition during the software's lifetime lets you inhibit notifications or the Plasma-specific night color mode.
'systemctl show ctrl-alt-del.target' shows data in nice machine-readable format. Any idea why 'systemctl show "*"' does not include ctrl-alt-del.target? Adding --type=target does not seem to help either. #systemd
Here's a thorough analysis of all the commits by "Jia Tan" from 2023-08 through 2024-03, showing the many legitimate code changes done before the introduction of the #xz#backdoor:
I’m impressed enough with native (systemd-nspawn) #NixOS containers that I think I’m going to use them for more parts of my home server as a way of providing a tad bit more isolation between services.
[#homelab#SelfHosting#SelfHosted#Linux#systemd ]
🐞 After a Recent SSH Vulnerability, Systemd Reduces Dependencies | Linuxiac
「 The rationale behind this request is to strip down libsystemd to its core functionalities, thereby reducing the risk of vulnerabilities that could compromise system security 」