Systemd by Example (2021)
seb.jambor.dev
Systemd by Example (2021)
1–10 of 115 posts
Re: Systemd by Example (2021)
#2This doc format works best for me ... just enough to get you started and get results. Digging deeper can be done where required. More like this!
Re: Systemd by Example (2021)
#3Related:
Systemd by Example - https://news.ycombinator.com/item?id=36817510 - July 2023 (11 comments)
Systemd by Example - https://news.ycombinator.com/item?id=30071240 - Jan 2022 (69 comments)
Systemd by Example – The Playground - https://news.ycombinator.com/item?id=30070159 - Jan 2022 (1 comment)
Re: Systemd by Example (2021)
#4This doc format works best for me ... just enough to get you started and get results. Digging deeper can be done where required. More like this!
also it is a whole series, there are the other parts as well! Great series, makes systemd understandable - and less fear inspiring.
https://seb.jambor.dev/posts/systemd-by-example-part-2-depen...
https://seb.jambor.dev/posts/systemd-by-example-part-3-defin...
https://seb.jambor.dev/posts/systemd-by-example-part-4-insta...
Re: Systemd by Example (2021)
#5I like it
Re: Systemd by Example (2021)
#6Systemd is a pretty neat little thing. It's what keeps me running Ubuntu and Debian servers instead of switching to Alpine, at least in those situations where I can't containerize what I want to do.
The thing that got me into it was systemd timers. I really like being able to split up what should run from when should it run. `cron` works best if you desire simplicity above all else, and Slack used `cron` for a very long time before moving to something more custom. But I ultimately don't feel like the learning curve for systemd timers is that bad, and the benefits it can bring (like writing all your echo statements to journalctl instead of some random hard coded logfile in a script) feel very worth it to me.
Re: Systemd by Example (2021)
#7Systemd is a pretty neat little thing. It's what keeps me running Ubuntu and Debian servers instead of switching to Alpine, at least in those situations where I can't containerize what I want to do. The thing that got me into it was systemd timers. I really like being able to split up what should run from when should it run. `cron` works best if you desire simplicity above all else, and Slack used `cron` for a very l…
>`cron` works best if you desire simplicity above all else
It may be simple, but it's config file is hard to comprehend compared to a systemd timer. Being able to just use "Friday 17:00" or "hourly" is so much more readable.
Re: Systemd by Example (2021)
#8Systemd is a pretty neat little thing. It's what keeps me running Ubuntu and Debian servers instead of switching to Alpine, at least in those situations where I can't containerize what I want to do. The thing that got me into it was systemd timers. I really like being able to split up what should run from when should it run. `cron` works best if you desire simplicity above all else, and Slack used `cron` for a very l…
>`cron` works best if you desire simplicity above all else It may be simple, but it's config file is hard to comprehend compared to a systemd timer. Being able to just use "Friday 17:00" or "hourly" is so much more readable.
While I support systemd timers over cron, AFAIK cron has stuff like @hourly.
Re: Systemd by Example (2021)
#9Personally I find systemd man pages pretty great, they comprehensively explain pretty much every thing that you need to know. Sure, they are more of a reference than a tutorial and there is lot of material to read there, but still I'd recommend reading the relevant sections whenever you are working with systemd
https://www.freedesktop.org/software/systemd/man/latest/syst...
Re: Systemd by Example (2021)
#10I was finally impressed with systemd when I recently had to port our single-process multi threaded TCP/UDP server (listening on a heap of ports) at work to a multiple binary/process, single threaded asynchronous IO system.
PartOf= let us still have one top level “lithium” service to start and stop which starts and stops all of the other services, while being able to use journalctl to view them as one log file via a wildcard!
Super nice, it’s been quite lovely.