Earlier quoted context omitted.
I'm not a Linux expert, but I thought that systemd was generally hated?
> bedrock of delight It might be sarcasm?
[deleted]
Systemd 252
11–20 of 317 posts
Re: Systemd 252
#12I love systemd for deploying Golang, especially the security features, that systemd can own the TCP port for zero downtime deployments of the application and restarts of a fail-fast application. It kind of replaced Docker (dockerd) which I've used with deploying Scala and TS.
Re: Systemd 252
#13People who want to use it can use it.
I am thankful for the non-systemd distributions, which are listed at https://nosystemd.org ; just scroll down to the list if you want to skip the advocacy.
Re: Systemd 252
#14I love systemd for deploying Golang, especially the security features, that systemd can own the TCP port for zero downtime deployments of the application and restarts of a fail-fast application. It kind of replaced Docker (dockerd) which I've used with deploying Scala and TS.
Hey, someone rediscovered xinetd
Re: Systemd 252
#15Systemd is without doubt one of the most important items of software on a modern Linux today, except perhaps for the Linux kernel itself. It turned the mess of shell scripts and other crap into the rock-solid, foundational system services layer we enjoy nowadays. If we do ever get the year of the Linux Desktop, we will have to thank the authors of systemd for giving us a bedrock of delight to build upon.
I'm not a Linux expert, but I thought that systemd was generally hated?
It's one of those things where people who hate it talk a lot about that, but people who like it don't have much to say.
Re: Systemd 252
#16Earlier quoted context omitted.
I'm not a Linux expert, but I thought that systemd was generally hated?
I would say it really depends on the context! Some reasons systemd is bad: - Its a "big" for small docker containers (which is part of why a lot of people like Alpine Linux). - It produces binary logs, which might not work with your workflow and is a kind of vendor lock-in if you don't script a binary-to-text script. - the binaries are all a lot bigger in terms if SLOC and in terms of storage space than the solutions…
> Its a "big" for small docker containers
Aside size, last I looked it required a lot of hoop-jumping to get systemd to run inside docker at all.
Re: Systemd 252
#17Systemd is without doubt one of the most important items of software on a modern Linux today, except perhaps for the Linux kernel itself. It turned the mess of shell scripts and other crap into the rock-solid, foundational system services layer we enjoy nowadays. If we do ever get the year of the Linux Desktop, we will have to thank the authors of systemd for giving us a bedrock of delight to build upon.
I wish Windows ran systemd--seriously. Windows services and low level functionality is just a hot mess of cruft, decade plus old UI and configs, etc. Please jettison it all and give a consistent declarative way to manage it all like systemd does for Linux.
Re: Systemd 252
#18I love systemd for deploying Golang, especially the security features, that systemd can own the TCP port for zero downtime deployments of the application and restarts of a fail-fast application. It kind of replaced Docker (dockerd) which I've used with deploying Scala and TS.
Hey, someone rediscovered xinetd
I remember using xinetd, and while xinetd does do the job… sometimes… systemd is much more comprehensive, so you don’t need to fuss about with different configs for xinetd, cron, init.d, etc. This is especially nice since the number of config options has skyrocketed, so systemd really simplifies administration (in my experience, at least).
Re: Systemd 252
#19I love systemd for deploying Golang, especially the security features, that systemd can own the TCP port for zero downtime deployments of the application and restarts of a fail-fast application. It kind of replaced Docker (dockerd) which I've used with deploying Scala and TS.
Hey, someone rediscovered xinetd
> Hey, someone rediscovered xinetd
1. http://0pointer.de/blog/projects/systemd.html
Replacing inetd was a systemd design goal.
2. Snark for someone learning is a bad move.
Re: Systemd 252
#20Earlier quoted context omitted.
I would say it really depends on the context! Some reasons systemd is bad: - Its a "big" for small docker containers (which is part of why a lot of people like Alpine Linux). - It produces binary logs, which might not work with your workflow and is a kind of vendor lock-in if you don't script a binary-to-text script. - the binaries are all a lot bigger in terms if SLOC and in terms of storage space than the solutions…
> Its a "big" for small docker containers Aside size, last I looked it required a lot of hoop-jumping to get systemd to run inside docker at all.
I think the idea of running systemd inside docker (or vice versa) is a little redundant to begin with—systemd and docker share a number of features.