Systemd provides huge advantages for administering desktops and servers as well. I'd actually go so far as to say those are the main reasons that systemd won (it's the default init system for all of the top ten Linux distributions by marketshare).
Systemd provides huge advantages for administering desktops and servers as well. I'd actually go so far as to say those are the main reasons that systemd won (it's the default init system for all of the top ten Linux distributions by marketshare).
Can you list some of them?
Seeing the logs of every service is also trivial since it's standardized. No more spelunking through /var/log or some random location.
There's also other parts I'm probably forgetting right now, but in general having a standard interface for service interaction is really, really useful.
Sometimes I get the impression that Linux folks underestimate the benefits of standardization. For example there's still no good, standard way to check the exact name and version of a distribution. If they can't agree about something as banal as that... (I think there is a convergence towards /etc/os-release, but when was the first distro launched? 1992? :) )
Unless you expect anything but most trivial use cases, e.g. some user-owned directory under /var/run (/run). Then you need to wild-guess at what combination of options needs to be set. Good thing that those options are at least described in docs.
> Seeing the logs of every service is also trivial since it's standardized. No more spelunking through /var/log or some random location.
syslog already was standard. We gained nothing really from journald.
What do I type in my terminal?
And about that "quick" part, I'd rather have a way to do that that's either easy to recall or easy to re-develop. journald's magical incantations that don't compose to any consistent language (unlike Vim or Emacs keybindings, for instance) nor are the same as in virtually any other software are not convenient by any stretch. I have my memory cluttered enough by half a dozen of different languages I use, their runtimes, runtimes of languages I don't write in but need for some software I run, twice that of DSLs and specialized languages, options and functions of dozens of services, wire formats of network protocols, management procedures of various Linux subsystems, and so on. I don't need an option to a command to tell me what you ask, I can work my way through grep/sed/awk faster than you read man page, thank you very much.
The real question is:
> I have two service from totally different origins. What do I type in my terminal to see their logs, with syslog or other widely used init systems currently in use, except for systemd?
So? :)
At some point Unix will learn that in the wild opt-out is better than opt-in. When you make doing the right thing easy, everyone will do it. When you don’t, everyone does what they want, which is generally bad.
The fact that we have to ag or grep -R is a kludge. There’s NO technical reason the folder structure shouldn’t be flexible but standardized and also NO reason why there shouldn’t be some system scaffolding to help with that. Call it systemd or whateverd, it should be there.
But sensible defaults are important. Software design is important. Unix basically skirts the issue by throwing all these decisions in the user's lap. I can take these decisions, but I don't always want to have to do it. And there's many situations where you can't necessarily do it, either due to technical limitations, political limitations, budget constraints, etc.
In short, I'm glad systemd is winning. Sure, the average user loses a bit on the purity front but he gains a lot on the practical front.
* http://jdebp.eu./Softwares/nosh/guide/logging-cheatsheet.htm...
Well, this is my luck: /var/log/boot, written by bootlogd, which is installed from distribution packages on Debian. So? What of it?
lsb_release -a?
(lsb = Linux standard Base)
(It should be noted that while our company runs an awful lot of 1st party stuff, what our team works with is exclusively 3rd party stuff over which we have precisely no control)
I was initial skeptical about their benefit - after all, an init script is just shell, it can be debugged literally with `sh -x`.
But that also means a) people write/ship fucking terrible init scripts, mostly because b) it's not necessarily simple to write an init script in pure shell.
The problem with systemd is the politics and the project's approach to the community (including their self-defined role/goals).
But note that unit files along with their PID 1 cannot be debugged now. Which is a big step backwards.
Sure, I'll concede that. But, due to their nature, there's also less need for ops/packager level users to debug unit files.
* https://unix.stackexchange.com/questions/428615/
* https://unix.stackexchange.com/questions/428689/
* https://unix.stackexchange.com/questions/428474/
* https://unix.stackexchange.com/questions/427836/
* https://unix.stackexchange.com/questions/427806/
* https://unix.stackexchange.com/questions/427712/
* https://unix.stackexchange.com/questions/427710/
That's just one WWW site, just the ones that I encountered (because I do not read them all), and just since the beginning of this month.
* http://uselessd.darknedgy.net./ProSystemdAntiSystemd/
* http://blog.darknedgy.net/technology/2015/09/05/0/
* http://jdebp.eu./FGA/run-scripts-and-service-units-side-by-s...
I simply gave an example of how it's an improvement over e.g. sysvinit.
The Uselessd Guy has some rather sharp comments, such as "you’ve been living under a rock for years", for that sort of thing. Even the Debian Hoo-Hah involved analysis of four systems.
"The politics" that you critique include failures to look around and learn from (and indeed about) what already exists and has been done. Don't make the same mistake.
One person asked about advantages of systemd. I listed one, and acknowledged systemd has issues.
I didn't compare it to any specific init system. I didn't even claim that systemd is overall better or worse.
I literally said:
> Declarative system service configuration files are an advantage