Many years ago, I used to work in infosec. One of my employer’s clients was a big and famous brand well-established in the luxury sector. One day, a colleague of mine was sent to test their POS. Inside one, he found a single transaction for around 6M € from a credit card swipe. It wasn’t a payment made from a bank transfer or a check, just a single credit card swipe! At the time, I couldn’t even dream a card with such a credit allowance would exist. I had a pretty good living then, with money for the rent, daily expenses, and even some savings. Still, for an instant, I remember feeling like a poor child living in a house made of mud.
I agree. Seeing stuff like that and how, more often than not, the clients treated their employees and consultants was just bad for the soul. In such contexts, you understand why workers aren’t called people but “resources.” In the end, I got burned out and quit the job.
My problem with systemd is that since I’m practically forced to use it that it’s flakey in starting services after boot (independent of service and distro). Since systemd I had to install monit to check if all services came up. Didn’t had that problem before. Or I forgot, it’s been a while…
Don’t worry about the downvotes, Lemmy is a systemd sausage fest. If you want negative “karma”, just write “systemd bad” or even “pulseausio bad” anywhere, and wait…
Well yes, if you don't provide intelligible arguments it doesn't deserve better. And a lot of the arguments really are like that: "systemd bad" or "is monolithic blob" (which it isn't).
Lol. Thanks. I really don’t care. I’m running linux servers professionally since the late 90s, which means I have seen one or the other WTF. And systemd had quit some of them, especially flooding log files and race conditions. For example see github.com/systemd/systemd/issues/7293. That took more than 2 years to fix. And if people like to downvote my personal experience with it they are welcome to do so. I mean all I did was answering a question why one might use a systemd free distribution. Oh and for the downvoters: SYSTEMD IS MICROSOFTS ATTEMPT TO KILL LINUX! Poettering always was their agent. en.m.wikipedia.org/wiki/Lennart_Poettering😉
systemd does have one problem that also existed before: sometimes services come with buggy unit files (or copy/pasted from something else and modified), similar to how there were all kinds of buggy scripts before. Unit files are much simpler than scripts and it should be easier to get right but when the author sometimes doesn't consider dependencies or test fail scenarios...
Use systemctl --failed to see which services didn’t come up, systemctl status SERVICENAMEHERE to see some status info about a service, and journalctl -b -u SERVICENAMEHERE to see all log messages generated by a service since last reboot.
The foreign bacteria in your gut had a much more direct audience with your brain than your cells do. Question is, is it an Embassy? Are they Diplomats? … or are they Oligarchs? >!As long as they call me sugar mommy for giving them sweets!<
Systemd is huge. It’s a complex project that covers not just the init system, but also process management, networking, mounts, sessions, many other things. Many people think its monolithic design run counter with the Unix philosophy and wish to use distros without systemd.
Just to avoid misunderstandings: it's not a monotolithic blob, it is thought so because its first project was a system daemon that manages system services. It is described as "a software suite that provides an array of system components for Linux operating systems.", it is highly modular and offer many optional components that each have their own purpose.
lemmy.ml
Active