this post was submitted on 29 Jun 2023
132 points (96.5% liked)
Linux
48165 readers
805 users here now
From Wikipedia, the free encyclopedia
Linux is a family of open source Unix-like operating systems based on the Linux kernel, an operating system kernel first released on September 17, 1991 by Linus Torvalds. Linux is typically packaged in a Linux distribution (or distro for short).
Distributions include the Linux kernel and supporting system software and libraries, many of which are provided by the GNU Project. Many Linux distributions use the word "Linux" in their name, but the Free Software Foundation uses the name GNU/Linux to emphasize the importance of GNU software, causing some controversy.
Rules
- Posts must be relevant to operating systems running the Linux kernel. GNU/Linux or otherwise.
- No misinformation
- No NSFW content
- No hate speech, bigotry, etc
Related Communities
Community icon by Alpár-Etele Méder, licensed under CC BY 3.0
founded 5 years ago
MODERATORS
you are viewing a single comment's thread
view the rest of the comments
view the rest of the comments
Right. But on something more complicated than initializing the usual daemon, systemd has all the same problems. For example, if you have a java application and you want to dynamically manage java parameters and application parameters, the script will look like a pain. something like bash -c 'java ...' or you will have to call a separate script in the initiator. And then to turn off the shell and switch to the application itself, there will be a whole adventure with pid generation.
But sure systemd really more easy then system V.
If you mean you want to auto-detect appropriate values that is no more complicated than the init script was before. You just call that wrapper script.
If you mean you want to turn those on and off as part of your local configuration that is actually quite easy with drop-ins in systemd, much easier than modifying the init script and then having issues with the package overwriting your script with a new copy.
I don't deny that systemd is easier than SysV. I say that on complex configurations it is not slightly simpler. Moreover, what I could do just in the sysV script, I now have to divide by tmpfiles.d and systemd. And sometimes even include processing both there and there, because depending on the version systemd has different behavior with parameters LogsDirectory= and RuntimeDirectory=. As a result, the dependence on the system has not completely disappeared for the package maintainer. Although of course there are a little less problems with systemd.
On other side as a user, I don't really like to guess exactly how a folder was created in /run, via tmpfiles or via systemd.
UPD: On SysV I have one complex, heavy script. Now I have the systemd service, the tmpfiles configuration, the /etc/conf.d parameters file and there is still a shell script to run. But if user wants reconfig something he need look 4 files instead one.