#Systemd

stfnNew blog post! I've been using TLS certificates generated by Tailscale to access my self-hosted, private services with HTTPS for some time now, but there is one problem with them: they do not auto-regenerate. So I used some bash and.. *thunder*, *ominous music* systemd to create an automated task that autoregenerates them periodically. To crank the fun to 11, I also use <a href="https://ntfy.sh" rel="nofollow noopener" target="_blank">https://ntfy.sh</a> to notify me if the task succeeded or not <a href="https://stfn.pl/blog/78-tailscale-certs-renew/" rel="nofollow noopener" target="_blank">https://stfn.pl/blog/78-tailscale-certs-renew/</a> <a href="https://fedi.stfn.pl/tags/blog" class="mention hashtag" rel="nofollow noopener" target="_blank">#blog</a> <a href="https://fedi.stfn.pl/tags/tailscale" class="mention hashtag" rel="nofollow noopener" target="_blank">#tailscale</a> <a href="https://fedi.stfn.pl/tags/systemd" class="mention hashtag" rel="nofollow noopener" target="_blank">#systemd</a> <a href="https://fedi.stfn.pl/tags/lxc" class="mention hashtag" rel="nofollow noopener" target="_blank">#lxc</a> <a href="https://fedi.stfn.pl/tags/nextcloud" class="mention hashtag" rel="nofollow noopener" target="_blank">#nextcloud</a>

feuerrotIs it somehow possible to specify additional options to <a href="https://chaos.social/tags/journalctl" class="mention hashtag" rel="nofollow noopener" target="_blank">#journalctl</a>'s grep function? I usually need some sort of `grep -C` for logfiles and it looks like that isn't possible using only journalctl options.<a href="https://chaos.social/tags/systemd" class="mention hashtag" rel="nofollow noopener" target="_blank">#systemd</a>

mborus<a href="https://mastodon.social/tags/TIL" class="mention hashtag" rel="nofollow noopener" target="_blank">#TIL</a> I learned, why my debian <a href="https://mastodon.social/tags/Python" class="mention hashtag" rel="nofollow noopener" target="_blank">#Python</a> <a href="https://mastodon.social/tags/systemd" class="mention hashtag" rel="nofollow noopener" target="_blank">#systemd</a> service output wasn't live updating in journalctl. This was a problem which I "temporarily" solved by using screen or tmux when I need to follow the output live. (= for about a decade or so...)Turns out I just need the flag "-u" for unbuffered output and to set the StandardOutput/-Error to "journal" (which should be the default anyway)And then suddenly after reloading "sudo journalctl -fu my_service" will produce a live, updating output.

bluca<a href="https://fosstodon.org/tags/systemd" class="mention hashtag" rel="nofollow noopener" target="_blank">#systemd</a> v258~rc1 is out for testing! So far it has been a complete, utter, unmitigated success, although that might only be because nobody has ran it yet. Time will tell.<a href="https://github.com/systemd/systemd/releases/tag/v258-rc1" rel="nofollow noopener" translate="no" target="_blank">https://github.com/systemd/systemd/releases/tag/v258-rc1</a>

musicmatze :rust: :nixos:Hey <a href="https://mastodon.social/@systemdUltras" class="u-url mention" rel="nofollow noopener" target="_blank">@systemdUltras</a> <a href="https://social.linux.pizza/tags/systemd" class="mention hashtag" rel="nofollow noopener" target="_blank">#systemd</a> <a href="https://social.linux.pizza/tags/systemdultras" class="mention hashtag" rel="nofollow noopener" target="_blank">#systemdultras</a>How to pause a timer during the execution of a service?Usecase: I have a timer that does a mail-sync every 10 or 15 minutes. I have another timer that does a backup every day at 11. During the run of the backup, I want to pause the mail-sync.I bet there's a way to properly do this with systemd - I am just not sure what the right way is.Btw, both of these services are user-services, if that matters.

ilyessLong story short, I broke my <a href="https://mastodon.online/tags/Linux" class="mention hashtag" rel="nofollow noopener" target="_blank">#Linux</a> installation. Let me know if you can relate x)<a href="https://ilyess.cc/posts/how-i-broke-my-linux-installation/" rel="nofollow noopener" translate="no" target="_blank">https://ilyess.cc/posts/how-i-broke-my-linux-installation/</a><a href="https://mastodon.online/tags/blog" class="mention hashtag" rel="nofollow noopener" target="_blank">#blog</a> <a href="https://mastodon.online/tags/systemd" class="mention hashtag" rel="nofollow noopener" target="_blank">#systemd</a>

Nik | Klampfradler 🎸🚲I got back to <a href="https://toot.teckids.org/tags/WebIDAMd" class="mention hashtag" rel="nofollow noopener" target="_blank">#WebIDAMd</a>, a <a href="https://toot.teckids.org/tags/systemd" class="mention hashtag" rel="nofollow noopener" target="_blank">#systemd</a>-userdbd-based system for using <a href="https://toot.teckids.org/tags/OAuth" class="mention hashtag" rel="nofollow noopener" target="_blank">#OAuth</a> / <a href="https://toot.teckids.org/tags/OIDC" class="mention hashtag" rel="nofollow noopener" target="_blank">#OIDC</a> / <a href="https://toot.teckids.org/tags/REST" class="mention hashtag" rel="nofollow noopener" target="_blank">#REST</a> identity providers for <a href="https://toot.teckids.org/tags/Linux" class="mention hashtag" rel="nofollow noopener" target="_blank">#Linux</a> system authentication.And I can now show off a first demo (no <a href="https://toot.teckids.org/tags/PAM" class="mention hashtag" rel="nofollow noopener" target="_blank">#PAM</a> authentication yet, but user and group listing):<a href="https://asciinema.org/a/728567" rel="nofollow noopener" translate="no" target="_blank">https://asciinema.org/a/728567</a>In contrast to <a href="https://toot.teckids.org/tags/sssd" class="mention hashtag" rel="nofollow noopener" target="_blank">#sssd</a>'s recent OIDC module, WebIDAMd is fully provider-agnostic and integrates transparently with userdbd, the current/upcoming standard in most Linux distributions instead of requiring a full separate software stack.

openSUSE LinuxIs <a href="https://fosstodon.org/tags/dracut" class="mention hashtag" rel="nofollow noopener" target="_blank">#dracut</a> your go-to for <a href="https://fosstodon.org/tags/initrds" class="mention hashtag" rel="nofollow noopener" target="_blank">#initrds</a>? It might be time for a mindset shift. This <a href="https://fosstodon.org/tags/oSC25" class="mention hashtag" rel="nofollow noopener" target="_blank">#oSC25</a> talk dives into <a href="https://fosstodon.org/tags/mkosi" class="mention hashtag" rel="nofollow noopener" target="_blank">#mkosi</a>-initrd, which is a faster, package-based way to build initrds, used on <a href="https://fosstodon.org/tags/Tumbleweed" class="mention hashtag" rel="nofollow noopener" target="_blank">#Tumbleweed</a> and backed by <a href="https://fosstodon.org/tags/systemd" class="mention hashtag" rel="nofollow noopener" target="_blank">#systemd</a> devs. Built from RPMs, no third-party surprises. <a href="https://youtu.be/p78J3Ql7D6s?si=JbKZpq9fFb3Oesr9" rel="nofollow noopener" translate="no" target="_blank">https://youtu.be/p78J3Ql7D6s?si=JbKZpq9fFb3Oesr9</a>

Klaus FrankAnyone know how to make one <a href="https://chaos.social/tags/systemd" class="mention hashtag" rel="nofollow noopener" target="_blank">#systemd</a> unit depend upon another but in a way that ensures that the unit(s) it depends upon have already been started even though they're of Type=idle?Funnily sddm stops the getty@tty1.service as part of its startup shortly after again too. So I don't even know why it is needed to begin with...

Klaus FrankAnother day, another issue related to <a href="https://chaos.social/tags/systemd" class="mention hashtag" rel="nofollow noopener" target="_blank">#systemd</a> Figured out why <a href="https://chaos.social/tags/sddm" class="mention hashtag" rel="nofollow noopener" target="_blank">#sddm</a> didn't work when forced into wayland mode without an xserver (or when the x11 configuration is missing). While gdm (which defaults to wayland) "just works".The sddm developers are currently struggling with an <a href="https://chaos.social/tags/systemd" class="mention hashtag" rel="nofollow noopener" target="_blank">#systemd</a> issue. Apparently sddm needs getty@tty1.service to have completed execution. But because it is of "Type=idle" the sddm service starts too soon and crashes...Funnily the systemd docs don't cover this...

JdeBP<a href="https://social.coop/@foolishowl" class="u-url mention" rel="nofollow noopener" target="_blank">@foolishowl</a> <a href="https://ioc.exchange/@azonenberg" class="u-url mention" rel="nofollow noopener" target="_blank">@azonenberg</a> <a href="https://mastodon.social/@mcc" class="u-url mention" rel="nofollow noopener" target="_blank">@mcc</a> <a href="https://hachyderm.io/@dalias" class="u-url mention" rel="nofollow noopener" target="_blank">@dalias</a> <a href="https://mastodon.social/@whitequark" class="u-url mention" rel="nofollow noopener" target="_blank">@whitequark</a> <a href="https://tech.lgbt/@becomethewaifu" class="u-url mention" rel="nofollow noopener" target="_blank">@becomethewaifu</a> Heh! It was, it turns out, and the only response stated to send it back to being a <a href="https://tty0.social/tags/systemd" class="mention hashtag" rel="nofollow noopener" target="_blank">#systemd</a> bug.<a href="https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1086055" rel="nofollow noopener" translate="no" target="_blank">https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1086055</a><a href="https://tty0.social/tags/Debian" class="mention hashtag" rel="nofollow noopener" target="_blank">#Debian</a> policy ping-pong. (-:

Marcos Dione<a href="https://en.osm.town/tags/til" class="mention hashtag" rel="nofollow noopener" target="_blank">#til</a> the bad way that, at least on <a href="https://en.osm.town/tags/debian" class="mention hashtag" rel="nofollow noopener" target="_blank">#debian</a> unstable, launching a long running process in <a href="https://en.osm.town/tags/screen" class="mention hashtag" rel="nofollow noopener" target="_blank">#screen</a> (but <a href="https://en.osm.town/tags/tmux" class="mention hashtag" rel="nofollow noopener" target="_blank">#tmux</a> and nohup and other seem to also be impacted) is not enough to survive a session logout, seemingly because <a href="https://en.osm.town/tags/systemd" class="mention hashtag" rel="nofollow noopener" target="_blank">#systemd</a> changed something more than 6y ago and now you have to mark users as linger-able to keep the feature working. Stay tuned.<a href="https://en.osm.town/tags/SysAdmin" class="mention hashtag" rel="nofollow noopener" target="_blank">#SysAdmin</a> <a href="https://en.osm.town/tags/Linux" class="mention hashtag" rel="nofollow noopener" target="_blank">#Linux</a>

JdeBP<a href="https://social.coop/@foolishowl" class="u-url mention" rel="nofollow noopener" target="_blank">@foolishowl</a> <a href="https://ioc.exchange/@azonenberg" class="u-url mention" rel="nofollow noopener" target="_blank">@azonenberg</a> <a href="https://mastodon.social/@mcc" class="u-url mention" rel="nofollow noopener" target="_blank">@mcc</a> <a href="https://hachyderm.io/@dalias" class="u-url mention" rel="nofollow noopener" target="_blank">@dalias</a> <a href="https://mastodon.social/@whitequark" class="u-url mention" rel="nofollow noopener" target="_blank">@whitequark</a> <a href="https://tech.lgbt/@becomethewaifu" class="u-url mention" rel="nofollow noopener" target="_blank">@becomethewaifu</a> Declared a "wontfix" bug in <a href="https://tty0.social/tags/Debian" class="mention hashtag" rel="nofollow noopener" target="_blank">#Debian</a> back in 2024.I wonder whether it did get carried over to a policy bug.<a href="https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1085370#21" rel="nofollow noopener" translate="no" target="_blank">https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1085370#21</a><a href="https://tty0.social/tags/systemd" class="mention hashtag" rel="nofollow noopener" target="_blank">#systemd</a>

JdeBP<a href="https://mastodon.social/@mcc" class="u-url mention" rel="nofollow noopener" target="_blank">@mcc</a> <a href="https://hachyderm.io/@dalias" class="u-url mention" rel="nofollow noopener" target="_blank">@dalias</a> <a href="https://mastodon.social/@whitequark" class="u-url mention" rel="nofollow noopener" target="_blank">@whitequark</a> <a href="https://tech.lgbt/@becomethewaifu" class="u-url mention" rel="nofollow noopener" target="_blank">@becomethewaifu</a> It didn't replace van Smoorenberg init+rc. It replaced Upstart. The existence of Upstart is the part of history that many people forget or gloss over.van Smoorenberg init+rc always was a straw man. The Debian committee included it, but everyone acknowledged at the time that the main contenders were systemd, Upstart, and OpenRC.<a href="https://tty0.social/tags/systemd" class="mention hashtag" rel="nofollow noopener" target="_blank">#systemd</a> <a href="https://tty0.social/tags/Upstart" class="mention hashtag" rel="nofollow noopener" target="_blank">#Upstart</a>

JdeBP<a href="https://mastodon.social/@mcc" class="u-url mention" rel="nofollow noopener" target="_blank">@mcc</a> <a href="https://hachyderm.io/@dalias" class="u-url mention" rel="nofollow noopener" target="_blank">@dalias</a> <a href="https://mastodon.social/@whitequark" class="u-url mention" rel="nofollow noopener" target="_blank">@whitequark</a> <a href="https://tech.lgbt/@becomethewaifu" class="u-url mention" rel="nofollow noopener" target="_blank">@becomethewaifu</a> Changing compiler is not the problem. But changing the standard library becomes one. systemd gained problems with <a href="https://tty0.social/tags/musl" class="mention hashtag" rel="nofollow noopener" target="_blank">#musl</a> because of this.<a href="https://tty0.social/tags/systemd" class="mention hashtag" rel="nofollow noopener" target="_blank">#systemd</a> <a href="https://tty0.social/@JdeBP/114646325165347305" rel="nofollow noopener" translate="no" target="_blank">https://tty0.social/@JdeBP/114646325165347305</a>

okanogen VerminEnemyFromWithin<a href="https://mastodon.social/@Tesseks" class="u-url mention" rel="nofollow noopener" target="_blank">@Tesseks</a> Debian should set up ntp (network time protocol) by default in the installation based on where you say your locaton is, unless if <a href="https://mastodon.social/tags/systemd" class="mention hashtag" rel="nofollow noopener" target="_blank">#systemd</a>-timsyncd decided to move the cheese on yet one more tried and tested thing to "make your life easier".

OSTechNixManage Linux Systemd Services Easily With Systemd-manager-tui <a href="https://floss.social/tags/systemd" class="mention hashtag" rel="nofollow noopener" target="_blank">#systemd</a> <a href="https://floss.social/tags/rust" class="mention hashtag" rel="nofollow noopener" target="_blank">#rust</a> <a href="https://floss.social/tags/systemctl" class="mention hashtag" rel="nofollow noopener" target="_blank">#systemctl</a> <a href="https://floss.social/tags/journalctl" class="mention hashtag" rel="nofollow noopener" target="_blank">#journalctl</a> <a href="https://floss.social/tags/linux" class="mention hashtag" rel="nofollow noopener" target="_blank">#linux</a> <a href="https://floss.social/tags/tui" class="mention hashtag" rel="nofollow noopener" target="_blank">#tui</a> <a href="https://floss.social/tags/opensource" class="mention hashtag" rel="nofollow noopener" target="_blank">#opensource</a> <a href="https://ostechnix.com/manage-linux-systemd-services-with-systemd-manager-tui/" rel="nofollow noopener" translate="no" target="_blank">https://ostechnix.com/manage-linux-systemd-services-with-systemd-manager-tui/</a>

FrançoisThe systemd project was and is a *huge* leap forward for Linux. I can't imagine doing sysops without it.<a href="https://blog.tjll.net/the-systemd-revolution-has-been-a-success/" rel="nofollow noopener" translate="no" target="_blank">https://blog.tjll.net/the-systemd-revolution-has-been-a-success/</a>Update: suspected "AI" usage for the images in the post, in case you want to avoid this.<a href="https://floss.social/tags/systemd" class="mention hashtag" rel="nofollow noopener" target="_blank">#systemd</a> <a href="https://floss.social/tags/Linux" class="mention hashtag" rel="nofollow noopener" target="_blank">#Linux</a> <a href="https://floss.social/tags/sysops" class="mention hashtag" rel="nofollow noopener" target="_blank">#sysops</a>

F. Maury ⏚Yop, Je viens de réuploader ma présentation éclair effectuée à Pass the Salt 2025, à propos du déploiement de secrets dans les infrastructures virtualisées en utilisant AF_VSOCK. J'ai ajouté des sous-titres en anglais et en français pour celleux que ça intéresse !<a href="https://peertube.stream/w/eidYHtjaeE6nZtTbpy722r" rel="nofollow noopener" translate="no" target="_blank">https://peertube.stream/w/eidYHtjaeE6nZtTbpy722r</a><a href="https://infosec.exchange/tags/pts25" class="mention hashtag" rel="nofollow noopener" target="_blank">#pts25</a> <a href="https://infosec.exchange/tags/terraform" class="mention hashtag" rel="nofollow noopener" target="_blank">#terraform</a> <a href="https://infosec.exchange/tags/systemd" class="mention hashtag" rel="nofollow noopener" target="_blank">#systemd</a> <a href="https://infosec.exchange/tags/secrets" class="mention hashtag" rel="nofollow noopener" target="_blank">#secrets</a> <a href="https://infosec.exchange/tags/infosec" class="mention hashtag" rel="nofollow noopener" target="_blank">#infosec</a> <a href="https://infosec.exchange/tags/vault" class="mention hashtag" rel="nofollow noopener" target="_blank">#vault</a>

Andriy UtkinA --privileged --cgroupns=host <a href="https://fosstodon.org/tags/docker" class="mention hashtag" rel="nofollow noopener" target="_blank">#docker</a> container launched with <a href="https://fosstodon.org/tags/systemd" class="mention hashtag" rel="nofollow noopener" target="_blank">#systemd</a> has taken over my machine, killing Xorg and capturing physical ttys. I guess I have let it, but I don't know what I could do differently to get it to run.

Recent searches

Search options

Administered by:

Server stats: