6 ms·
I'm a devop, not a system administrator. I setup and administered a number of single machine web services for my customers along the years, almost all of them w
by pmontra 12y ago
I'm a devop, not a system administrator. I setup and administered a number of single machine web services for my customers along the years, almost all of them with Debian plus some Ubuntus recently. Database, application server, web server. Nothing fancy. I also use Ubuntu as my primary desktop (some sort of gnome fallback DE) after I removed a lot of cruft if comes with by default.
From my experience what I need on a desktop is very different from what I need on a server. On a server I don't care about displays, keyboards, backlighting, sound, USB disks, mics, scanners etc. On my desktop they are very important. There are a number of companies offering Linux VPSes with 512 MB RAM and they can be good to host a low traffic web service. Good luck running a modern Linux DE on a 512 MB machine. Not impossibile but not very productive.
So I can imagine having very different init systems for desktops and servers if this means that the server won't be encumbered by a number subsystems which are of no use to it. Furthermore binaries instead of scripts and opaque log files leave a bad taste in my mouth. They make me figure a future with a Windows like event viewer to browse the log files, over a terminal based ssh connection. I'm quite concerned about it. It will waive one of the biggest advantages of a Linux server over a Windows one.
A fork, or an alternative init system, could be a good solution. We should run this experiment, pick what we like and don't harass the people on the other side. We will see the results after some years. The satisfaction of the admins will decree the winner.
- srean 12y agoWish I could upvote this a thousand times.
- grifferz 12y agosystemd has a number of features which are of interest to server operators, especially those who use containers, which may well be many of us before long. Running systemd as pid 1 does not imply running a desktop environment. I have plenty of VPS customers running systemd as pid 1 in 512MiB RAM. Running systemd as pid 1 doesn't imply having every single binary and subsystem of systemd running. I would encourage you to try it before deciding it's something you won't find useful. Avoiding it looks like it's going to be significant effort and you'd want to know for sure that you're justified in that before embarking on that course of action.
- pmontra 12y agoI'll look into that. Thanks!
- m45t3r 12y agoYep, this is true. The only thing I concluded from this page is "I am an old time Debian admin, I don't want to learn another way to configure my system that is not a bunch of shell scripts, so I am gonna bitch about this decision and create a fork". Actually, I find it's funny how anti-systemd people nowadays claim that "systemd is a init for desktop systems" since Gnome adopt something unrelated to the _init_ part of systemd that is the systemd-logind (that actually is a substitute of ConsoleKit that was deprecated god knows how many years ago). systemd has lots of features that makes sense on servers too. You may or may not need these features on your server, but systemd (as a init system) is still a better init system than sysvinit.
- LeonidasXIV 12y agoActually, systemd is pretty awesome for servers. I wrote a simple program that outputs to stdout and ran it under systemd. * it automatically cares about starting it * it automatically puts the programs stdout into the journal (from which I can filter the output of my specific program without having to syslog() everything) * it allows me to run the program as user with one line in the INI unit file * it allows to make the users home directory read-only (or even inaccessible), so in case someone takes over, there is only so much they can break * it can create a private /tmp for my program Actually, for desktops I don't care but for servers systemd is pretty awesome.
- Zancarius 12y agoYou hit on some of the points that won me over when I first started using systemd. Writing services is easy and logging their output is a breeze. Not having to fret with supervisor processes or daemonizing code shifts some of the complexity out of the application and into the init process[1] where I'd argue process management ought to live. Given that targeting sysvinit for all the various sysvinit-compatible systems out there can be an exercise in frustration (OpenRC, Debian, the *BSDs, all of whom have subtly different flavors for starting and stopping processes) better left to individual maintainers, it's nice that I can write a unit file and pretty much have it work on any system that's running systemd. [1] I'm aware that some people might argue additional complexity doesn't belong in an init. That's fine. You're probably right.
- andor 12y agoYou're spreading FUD. So I can imagine having very different init systems for desktops and servers if this means that the server won't be encumbered by a number subsystems which are of no use to it. systemd is about choice ;-) Only use the subsystems that you need. For example, if you'd want to save some memory and time, you could use systemd-networkd instead of shell scripts and dhclient. systemd is used in constrained environments like phones and embedded systems because it's fast and solves problems (e.g. watchdog chaining).
- monochr 12y agoSomeone disagreeing with you doesn't mean they are stupid, evil and part of a grand conspiracy to destroy everything you love. They just have different priorities. Why is this so hard for people to understand?
- XorNot 12y agoBecause a lot of people are speaking very authoritatively, yet with little content, about systemd. They raise objections based on partial or inaccurate information. Various bans on discussion are happening precisely because it's apparent that a number of people are no longer interested in useful discussion, so much as creating chaos until they get their way. Manifestly described by the idea that people without time to interact with Debian, are going to instead launch their own Linux distro.
- monochr 12y agoIf partial or inaccurate information about a subject was the criteria for not talking about it then Torvalds should have shut up about kernels and let Minix be the default for everything. Read the exchange between him and Tanenbaum and tell me it doesn't sound like two douche bags flame baiting each other with Torvalds sounding like he has no idea what he's talking about: http://oreilly.com/catalog/opensources/book/appa.html http://oreilly.com/catalog/opensources/book/appa.html The whole point of free licenses is to let half educated monkeys type away on keyboards because every so often you end up with Apache or Linux out of it, of course you also get pulse-audio and systemd but no system is perfect. If people like it more than Debian it will replace Debian, like Ubuntu nearly did before they went with unity and a whole bunch of other terrible decisions, if they don't it will die, and if it sticks around as a project with some users, like every other debian derivative, it will be a wonderful resource to find bugs.
- progman 12y ago> A fork, or an alternative init system, could be a good solution. I consider this a good idea. Servers and desktops are two different things so why not have two different Debian versions? This way Debian Server could be kept small and simple while the systemd developers could continue without any restrictions. If they go too far then we could use the Debian server and add our own desktops to it.
- asdfaoeu 12y agoA lot of the components mentioned are actually optional and you can build systemd without them or disable them at runtime. I'm guessing this idea that this idea that systemd is targeted for the desktop is from the logind kerfuffle with GNOME and friends but it's actually an optional component. If anything though systemd is more targeted towards server market.
- XorNot 12y agoThis. SystemD means you can boot the system without needing a shell installed at all which is what Debian has been proposing moving towards for a very minimal server image.
- digi_owl 12y agoOk, somebody has clearly jumped the shark!
- progman 12y agoFine. There speaks nothing against Debian Desktop for servers by admins who prefer systemd. I am current happy Debian user myself, and I would use such a system for my desktop. However regarding servers I agree with the Unix veterans that Unix(-like) systems should be faithful to the KISS philosophy which made Unix so great. The IT world has become very complex, and we should not make it more complex than necessary. Debian and its derived distris took over the server world, and (AFAIK) it accomplished that with SystemV not with systemd. So SystemV is not that bad.
- XorNot 12y agoYour log files are binary already. What do you think 'cat' is, other then a binary log reader? Binary log files are as easy to read as ASCII with the right translator. Tagged binary formats are easily and trivially self-describing, and as resistant to corruption as ASCII. The problem is, people think they'll be able to understand corrupt ASCII logs, but in reality basically never deal with them. They deal with truncated logs - which, well guess what, can be handled just as easily as for binary logs. Given that journald can be configured with a log size of 0, and to output everything straight to syslog, this is such a non-complaint it's absurd. Especially when the hot thing in syslog management is usually to stream everything into a database of some kind to make it easy to search! EDIT: Oh yeah, and this is assuming you're not compressing your logs. Which you probably are. In which case, they're already a very complicated, very corruptible non-binary format for which you have to use a fairly complicated read app (zcat) to access.
- e12e 12y agoGood points. As for compression: I think most people compress logs post-rotation. So you'll be unlikely to have a corrupted compressed log. Either the file will be compressed, then then original removed, or compression will fail, and the original will remain untouched. It's more of an issue with whatever is written to disk by running processes. As you point out, it's debatable whether or not unicode/ascii vs "binary" is a sensible distinction ... I'd say taking a hex-editor to a mangled but mostly ascii text file is easier than some (any) binary format, but perhaps you know of some easy-to-use tool that will take a file-description and give you back data? Things like figuring out integer encoding and offset for timestamps across different files etc... is much easier with a rather redundant ascii timestamp than some binary number? If your filesytem eats your files... well then that's a different problem.
- XorNot 12y agoExactly my point: this isn't a complex database format. It's a tagged binary format, written in an append only fashion. So you're only going to lose data if the tool decides to write bad data, but that's just as true of a text log format - your logs are useless if all those numbers don't actually relate to the values they claim to. So any tool which can read a journald journal can happily do so until it hits hard corruption - which is about as well as you ever do with syslog. I'll gladly trade an unlikely and really narrow recovery profile, for smaller, easily machine readable, well-defined log files (in the sense that, to write an entry, someone wrote down the exact struct somewhere, and had to keep using it that way. No regex's which fail in some case which happens once every 1 million lines of log file). Especially since the compatibility layer is just "forward text logs to syslog". Reference: http://www.freedesktop.org/wiki/Software/systemd/journal-files/ http://www.freedesktop.org/wiki/Software/systemd/journal-fil...