Honestly buttctl has some nice features once you get used to it.
I still stand by my assumption that anyone complaining about systemd has never tried to configure SysVInit scripts before
Been using Linux as my main system for about 8 years now. I know nothing but systemd. I have never tried other init systems, so I genuinely don’t know what I’m missing out on (if there is any). I don’t mind systemd and I really really like services and timers. I use them all the time to automate things, but that doesn’t mean I don’t hate some things about systemd. One of the things that I’d love to burn to charcoal is that “a stop job for UID 1000… 1:45 minutes”, bitch? I don’t have that much time on my hands, reboot right now. What are the things that other init systems have that make them better than systemd?
Enable SysRq commands and ALT+SysRq(same as print screen)+B to force reboot
You really shouldn’t do that. SysRq reboot is like SIGKILL on steroids. If the OS hasn’t flushed and closed every file handle, you can corrupt the shit out of the system. Ask me how I know.
You can skip waiting for services to stop by pressing Ctrl+C eight times within two seconds. If you really need to reboot using SysRq, then at least do a sync (Alt+SysRq+S) before that.
a stop job for UID 1000… 1:45 minutes
oh oh and then it changes to 3 minutes something when 1:45 passes! where was that configured mr poettering??
OP when systemd successfully wipes his ass
“It is I. Everything.”
Yay another thread where a bunch of script kiddies running a homelab come shitting on a toolset that saved the professionals from the init mess. But they of course know that systemd is bloated and prefer running their node servers in dokker containers on something more lightweight
This, so much this. Although it’s equally old grumpy farts as well as script kiddies. You’ll be able to identify the former by their trademark quote “Systemd is the end of / nail in the coffin for Linux”.
systemd was a solution in search of a problem. I saw it that way when it came along and still see it that way. I’m sure as usual that will ruffle the feathers of the zealots and fanatics. So be it. I’m not expressing their opinion on systemd but my own. I don’t see how its an improvement sysvinit. I can’ do the same things with both and indeed still maintain a sysvinit linux system that works just fine without systemd being involved.
systemd was a solution in search of a problem
Systemd solved lots of problems for me and made things easier so you know… I guess they succeeded.
Such as?
Such as initscripts being a nightmare to maintain, and insufficient for the complexity of a modern system. Read about it here: https://redlib.privacyredirect.com/r/archlinux/comments/4lzxs3/why_did_archlinux_embrace_systemd/
You didn’t realize there was a problem to solve because others, the distro maintainers and developers, worked their asses off to solve that problem for you.
Standard boiler plate response to not having had to ever do this. I started with Slackware Linux and still keep a installation around to keep up with how things work. I solve my own problems and its for that reason You’re explanation falls short. In truth it isn’t that difficult and it many ways preferable to not hand over control of services to one over reaching controller. I’ve had systemd hangup where sysv would have just kept on sailing.
Its perhaps because I have so much experience with both that I can truly see how systemd isn’t the cure all its purported to be.
who is being forced to use systemd and how are they forcing you?
Who are you asking?
Oh, I guess I’ll just downvote you too then.
