Our goal is to make GNOME OS a daily driver for QA and finalize the migration, but this work will be fundamental to the future of all secure image based / immutable Linux distributions.
hmmm
systemd-oomd is so confusing, memory OOM killer doesn't work since it is not monitored...
Specified my user service as documentation said, but it is needed to perform reload-daemon to work hmmm...
echo 1 to memory.oom.group is not also possible.
Anyone has an idea to make it reload every time I sign in?
Wenn ich ehrlich bin, habe ich darüber zu wenig Ahnung. Ist dies so anzuwenden und zu empfehlen oder wie seht ihr dies?
»Systemd-Alternative zu sudo soll Linux sicherer machen:
run0 lässt reguläre Benutzer Programme mit root-Rechten ausführen. Es ähnelt sudo, nutzt aber andere Mechanismen zur Privilegienerhöhung und soll sicherer sein.«
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?)
@starman
Systemd is nice. I miss GUI apps for #SystemD.
Permanent mounting a Network drive or creating new Services and inspect and modify is such a point.
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
Systemd wants to expand to include a sudo replacement (outpost.fosspost.org)