News for hackers. Stuff that matters.
Re:Working with Systemd Timers by linsomniac on Thursday March 13, 2025 @10:49PM (#43359173)
I'm convinced that the people who hate systemd are a small minority. They also happen to be fairly vocal, which I think makes them seem outsized.
Re:Working with Systemd Timers by jauntywundrkind on Thursday March 13, 2025 @11:16PM (#43359280)
I'd be excellent to see their complaints collected and elaborated. Because God Fucking Damn, these seem like some incredible whining Advanced Persistent Threats against anything getting better. If I were a pro-discord disruptor, I'd pay these people to keep at their endless grudges against every single person having to figure out ever single fucking capability de-novo.

Systemd makes so so so many incredibly good service administration capabilities easy & on tap. The main thing I want from systemd haters is to show how how how folks did things well before. Mostly I think this is a rebellion of the losers, people who hate having to do a good job, people who hate learning the many many many many ways we could run services better, who valorize each service figuring out their own unique special bespoke ways of running their stuff. Its fallen as fuck. We need need need the systemd socialization of running stuff well, controlling permissions & access. There's near zero precedent from the past of anyone else being responsible. That's just the situation. Systemd has drastically elevated what sysops can do, orthogonally to the service by service init launching of the past that got us no where.

Re:Working with Systemd Timers by DaSHacka on Friday March 14, 2025 @11:44AM (#43363736)
> I'd be excellent to see their complaints collected and elaborated.

https://web.archive.org/web/20250310201357/https://nosystemd...

Re:Working with Systemd Timers by pdimitar on Friday March 14, 2025 @01:01PM (#43364606)
I challenge the authors of this website to show me a software written in the last 10 years that never had a bug. I have scanned the first 20-ish items and it seems those are either fixed or not considered important (unsure about the latter; didn't give them too much reading as of the time this comment was written).

In general it seems it's just a collection of GitHub issues. The FQDNS thing seem to be people outraged at systemd for something that the Linux kernel does not (or did not?) do well with certain hostnames -- those ending with a dot.

And there are some security issues / CVEs which is regrettable and I hate it but again, show me software that does not have them.

Seems like a very petty way to just attack something from a cursory glance. The author(s) might have as well made a ClickHouse remote query directed at systemd's GitHub issue tracker. ¯\_(ツ)_/¯

Re:Working with Systemd Timers by michaelmrose on Sunday March 16, 2025 @02:48AM (#43377309)
This is ultimately such a weirdly aggressive comment. I don't feel like systemd or its alternatives drastically elevated what ops can do.

Most goals achievable in 2025 are those achievable in 1995.Its a small problem space without 30-60 years of headroom to explore and by simple logic most interesting things are going to be outside this fairly basic space.

It provided greater standardization and more power like 5 other options many of which existed prior with a simple syntax which is not without virtue.

Its just weird to refer to proponents of alternatives as "losers" who hate learning things when most proponents know systemd and other options.

Re:Working with Systemd Timers by throwaway314155 on Thursday March 13, 2025 @11:03PM (#43359225)
One might even go so far as to say they're a vocal minority.
Re:Working with Systemd Timers by DaSHacka on Friday March 14, 2025 @11:45AM (#43363748)
One might even go so far as to say all Linux users are a "vocal minority" to begin with.
Re:Working with Systemd Timers by linsomniac on Saturday March 15, 2025 @10:27AM (#43372755)
I'm familiar, but I broke it up that way for a reason.
Re:Working with Systemd Timers by MyOutfitIsVague on Friday March 14, 2025 @12:29AM (#43359575)
I think in general it's a shrinking minority. I was outspokenly critical of systemd in the past, but much about it has improved, and I have to admit it has made my life significantly easier in many ways. I'm still not a big fan of some things being systemd projects that don't really need to be under the umbrella (why is resolved even a systemd project? Or systemd-timesyncd?) but service definition and management, transient services, sockets, timers, and many many more things are pretty great. At this point, I pretty much love it. Even things that initially annoyed me, like timers, I've grown to love, not least because my cronjob entries are manageable files that I can commit and backup, and I can individually enable and disable them without having to deal with stupid commenting and such.

Checking service status and managing services is also significantly better with systemd than any other init system I've used, and I've used a lot over 15 years of systems administration.

I still find journald a bit annoying, though, and I still am not completely sold on binary log files. I understand the benefits, but working with them is still much more opaque than text logs.

Re:Working with Systemd Timers by linsomniac on Saturday March 15, 2025 @10:23AM (#43372727)
>I still find journald a bit annoying

I've come to like it. At first, probably around 15 years ago, I was kind of annoyed at it and just wanted my old /var/log/syslog back. But it has some really nice features, especially for log processing and tooling, like "show me logs from the last minute" (--since) or "show me logs from where I left off" (--cursor).