Ok #Linux nerds and neckbeards. Why does #Systemd list this (when using completion) even tho it's not existed for 10yrs on my system, is nowhere, and doesn't come up in list-units/list-unit-files.
Again, this file or pkg doesn't exist anywhere on my system and hasn't for 10 yrs. Maybe just a side effect of having a 10yr old install 
What is your opinion on systemd?
Gahhh, all the years using journalctl and searching for stuff without knowing there is grep option. Case sensitivity is longer option, but exists.
`journalctl -S yesterday -g sleep`
I’ve never really had an emotional response to #systemd and never really understood why people so strongly disliked it, or what objective or things that could be reasoned about.
After many years of using a #archlinux for a desktop and loosely paying attention to systemd features and adjacent features I think I get it. It does way too many things and is very complex.
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.
So the question is, where does #systemd get it from? I haven't had ntpsec for a long time.
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.
➤ 簡化容器管理，提升開發效率
✤ https://podman-desktop.io/blog/podman-quadlet
Podman Quadlets 是一種利用 Systemd 聲明式管理容器的新方法，適用於小型應用或開發環境，避免了 Kubernetes 的複雜性。Podman Desktop 擴展 “Podman Quadlet” 簡化了 Quadlets 的管理，提供視覺化界面來列出、生成、編輯和監控 Quadlets，讓使用者更容易地利用 Systemd 管理容器，實現自動啟動、重啟等功能。
+ 感覺這個 Quadlets 真的解決了在單機開發環境下使用 Kubernetes 的過重問題，Podman Desktop 的整合讓操作更方便了！
+ 終於可以告別繁瑣的指令了，透過圖形界面管理容器，對於新手來說很友善。
#Podman #容器 #Systemd #DevOps
cool, i now get push notifications via #ntfy when any #systemd service fails and it will include the logs as well! this is a lot better than manually checking the status and logs every morning.
i thought this would be impossible in #nix due to infinite recursion and that i would have to manually set OnFailure= for every service, but i found a blog post with an easy workaround instead:
https://medium.com/red6-es/systemd-service-failure-notification-system-92761903c557
New Blog post after 3 years: "Using a simple python script in NixOS as a systemd Service without packaging it" https://euer.krebsco.de/using-a-simple-python-script-in-nixos-as-systemd-service-without-packaging-it.html #nixos #systemd #python
Working with a volunteer group who has a relatively simple Python app deployed via Docker Compose.
What did they get from this? "Automatic restarts."
Wrote them a #systemd service definition to run the app out of a plain virtualenv. All the same benefits, way fewer moving parts in production.
"ParticleOS: Systemd's Very Own Linux Distro in Making".
"In its current state, ParticleOS seems well-suited for developers who want full control over their system."
Wrong. People who want full control over their system don't use systemd. You should face it.
And I'm daring to make a bold statement: This seems to me that here #systemd actually enhances and helps with the application of the #UnixPhilosophy of using a modular design with multiple, small services and interconnecting them.
By creating reliable connections between them. Or if some connection breaks unrecoverably to properly propagate this to all affected users. And by using a simple, short, descriptive, non-programmatic language for service files.
I have to say, I'm getting more comfortable with #systemd services. And I find it fascinating how with its templates and powerful dependency feature I could achieve some wild, very dynamic stacking of @gstreamer, @pipewire, #mpd, #mpv and #SAP / #RFC2974 with only a few lines for various systemd services. So for instance a #multicast SAP announcement of @schenklradio will only appear if something plays on that pipewire device, which only happens if that radio is on air and reachable.
