Hacker News Board Hacker News, browsed like a classic message board
Live data from Hacker News

Systemd by Example (2021)

seb.jambor.dev

Post reply on HN
Print view View original

11–20 of 115 posts

Re: Systemd by Example (2021)

#11

Post by hiAndrewQuinn »

charcircuit wrote: post #7
hiAndrewQuinn wrote: post #6

Systemd 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.

I started writing a "oh, I never found it that difficult" comment. Then I thought to test my own belief and tried to type out a cron schedule for "run this every hour", and... Well...

https://crontab.guru/#*_0/1_*_*_*

Oops. Point taken :)

Re: Systemd by Example (2021)

#12

Post by girvo »

hiAndrewQuinn wrote: post #6

Systemd 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…

journalctl alone makes it so good IMO

Re: Systemd by Example (2021)

#14

Post by jamesponddotco »

hiAndrewQuinn wrote: post #6

Systemd 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…

As a sysadmin, sandboxing and the general ease of use is what really sold systemd to me.

Re: Systemd by Example (2021)

#16

Post by caiusdurling »

hashworks wrote: post #8
charcircuit wrote: post #7

Earlier quoted context omitted.

>`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.

Some cron implementations do, it's not portable.

Re: Systemd by Example (2021)

#17

Post by andrewfromx »

funny, to me systemd == no docker, no containers, just a VM.

it's my goto way to keep my programming running and have it be restarted if the vm reboots. I use VMs like "pods". I deploy code directly to the VM and run it there along with other programs. I scale up and scale down with: https://www.pulumi.com/

Re: Systemd by Example (2021)

#18

Post by bheadmaster »

caiusdurling wrote: post #16
hashworks wrote: post #8

Earlier quoted context omitted.

While I support systemd timers over cron, AFAIK cron has stuff like @hourly.

Some cron implementations do, it's not portable.

Neither are systemd timers. I don't think there's a single system out there implementing the systemd timer interface.

Re: Systemd by Example (2021)

#19

Post by dale_glass »

bheadmaster wrote: post #18
caiusdurling wrote: post #16

Earlier quoted context omitted.

Some cron implementations do, it's not portable.

Neither are systemd timers. I don't think there's a single system out there implementing the systemd timer interface.

What do you mean? There's a single implementation as far as I know, deployed on many distributions and working identically.

Re: Systemd by Example (2021)

#20

Post by bruh2 »

andrewfromx wrote: post #17

funny, to me systemd == no docker, no containers, just a VM. it's my goto way to keep my programming running and have it be restarted if the vm reboots. I use VMs like "pods". I deploy code directly to the VM and run it there along with other programs. I scale up and scale down with: https://www.pulumi.com/

If I correctly understand your point, then it's worth noting the article is using a container merely to showcase the different parts of systemd in a sterile, reproducible environment. They're not running containers as systemd services, even though that's possible with podman

Love Pulumi btw

Post reply on HN