systemctl status wipe-my-butt.service
systemctl status wipe-my-butt.service
systemctl status wipe-my-butt.service
OP when systemd successfully wipes his ass
I like systemd
Awaiting the guillotine...
You're not alone. For most of my career, I've only used Linux to develop software and deploy that software to production. That usually means webservers, databases, iptables/netfilter, and all the other backend processes that glue that together.
Before systemd, I was using sysVInit. Let me say that systemd has been head-and-shoulders above the previous experience in a variety of ways, with a host of built-in features:
systemctl status <service>
shows you exactly what files are loaded)Bottom line: it's dead simple to add your own stuff, and just as simple to read what packaged software is doing. I also think that using a CLI (instead of poking around /var/run and ps
output) is a step up in terms of system administration, given how complex all this can get.
My only contention is the forced use of journald, where my preference would be to use the standard /var/log paradigm for all this, rather than have a doorman to a binary logging database. You can configure it to emit text logs, but that's not the system of record for logging - just a feed.
All that said, container-based solutions have rendered both init systems irrelevant a lot of the time, with tools like Kubernetes providing just about all of the same features. Moreover, cloud solutions tend to lean into cloud-init for host startup configuration and management anyway.
I am more of a hobbyist when it comes to running software on Linux. That said, I usually end up being the guy who installs and manages software on work Linux servers, writes Ansible scripts to standardize configs, and troubleshoot when things dont work. Im not as advanced as you are, but got my fair share of pre-systemd headaches... so yeah, I completely agree with you.
How do you add a custom service to systemd? Let's say /usr/local/sbin/foobar . I can never seem to get it to work, but can do it easily in sysvinit.
I love it as well it makes everything way easier. You can even run containers with it if you install quadlet. I just recreated most of my homelab containers using it.
Very cool! TIL
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".
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?
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??
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.
I just set the timeout time to 5 seconds.
Honestly buttctl has some nice features once you get used to it.
I like how you can pipe anything into it.
I've always liked systemd.
I'm learning FreeBSD and the training wheels are off having to learn RC. I should've done this years ago.
On that, anyone know how to pull core temps off a 20 year old Celeron D in OpenBSD? That and my internal PC speaker are the only things I don't have working yet.
"It is I. Everything."
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.
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.
It's almost as if people think systemd is one massive executable rather than a suite of tools
Nah, it's a single executable, like GNU.
All that happens at boot is that linux.exe calls systemd.exe, uses all your system resources making your machine unusable bloat.
None of this stuff for me. I prefer one tool doing one thing, like busybox
Initramfs is just a executable
Prove me wrong
Yes, GNU.exe, I know it well.
From all the hate you see, it does look like that. It is not?
The answer is more complex than a simple yes/no. Fortunately, an actual Arch Linux maintainer shared their experience with init scripts and why it was necessary to switch to systemd: https://redlib.privacyredirect.com/r/archlinux/comments/4lzxs3/why_did_archlinux_embrace_systemd/?
This line is particularly great:
Other than that, and especially in the case of Arch Linux, nobody is forcing anybody to use any other component of systemd, or as proven by the likes of Artix and Devuan, systemd itself.
Well it is also a massive executable in the mix there
An inbred set of separate entities right out of x-files "home" , that can only coexist with one another in a toxic bug-eyed gang? Yeah, it's "separate" pieces.
Now go mount a volume the normal way.
I still write my mounts in fstab