SystemD

>a stop job is running for...
your shitty daemon that refuses to exit

bricked some mobos.

Not systemd's fault
twitter.com/mjg59/status/693494314941288448

>Not vague terms like "bloat"
but systemd is significantly bloated and dismissing it because you feel it's a vague complaint only makes you come off as a zealot with nothing to add to the conversation, it's a large project which has its fingers in every part of your system from managing time to your containers and as a project it grows more every day, if you ever need to diagnose a simple issue with your dns you'll need to know and understand how systemd works which turns quick tasks into long afternoon reading verbose manpages that puts gnu manpages to shame

systemd was introduced as a simple init daemon and is now significantly more than that, it's the equivalent of people going to stackoverflow to ask how to add numbers in javascript and other people suggesting jquery

>Guess why most major distributions have switched to systemd
distros switched to systemd because it significantly reduces the burden of distro maintainers to write, manage and update hundreds of init scripts that generally aren't transferable to other distros, it has nothing to do with end users or administrators using systemd or its alternatives
systemd is also a dependency for gnome, if a distro wants to provide gnome they HAVE to support systemd

>just write a service file for that userland process that isn't a daemon but you want running in the background
can you imagine telling a window user that if they want their shutdown to work normally they have to write a service file for their program they keep in the task bar? poettering/rhel are going to kill linux on the desktop before it even gets out of the cradle

It's never been properly audited for backdoors and security flaws. For all the memes on here bashing itoddlers and the "just werks" mentality they have, almost all linux distributions have given up security for easier development.

>if a distro wants to provide gnome they HAVE to support systemd
That is not true. You can run Gnome 3 on Gentoo while using OpenRC and not having systemd installed at all.

gnome requires login1 dbus interface, it doesn't depend on systemd, stop spreading false information

These pieces of code also have never been audited for backdoors and security flaws:
- Linux
- SysVInit
- all those SysVInit scripts
- pretty much all server software you might be running on your GNU plus Linux system

Not liking cunny is pretty degenerate.

The lack of audit is not a valid reason to dismiss a software, considering it's a luxury that only few in the free software world can afford, it's also much less relevant for codebases that see rapid changes like systemd

*runs your start job for 90 seconds*
nothin personnel kid

What's causing it, by the way? When it happens, it seem to happen for no reason

It's less homosexualy named than it's alternatives.

Some daemons explicitly support systemd by utilizing its API, it basically notifies the service manager whether it's finished with its startup or if it failed, when there's a bug that prevents said daemon from notifying systemd, it's going to wait for 90 seconds by default, I think this can also happen if your service file incorrectly specifies Type=notify for daemons that don't use said API
freedesktop.org/software/systemd/man/sd_notify.html

So, basically buggy daemons can't properly tell SystemD about their status, right?

Yes

Any way I can't just tell SystemD to ignore that and boot anyway?

Also, again it's technically not SystemD fault

Just report the issue to your distro maintainers, in the meantime you could also lower the wait time

>in the meantime you could also lower the wait time
Thanks, kind of an obvious thing to do after you said it

[ *** ] (1 of 2) A stop job is running for Session c2 of user ... (3min 30s)

No, but it's still a security risks and systemd should take responsibility and add some sort of control on efivars if GRUB and so desperately need it

>systemd should taking responsibility for kernel bugs
i thought you guys hate bloat

This is a damn good reason, I’d say.
Stick with OpenRC

Attached: FF407B20-84E1-4D7E-9837-4696F2F12044.png (1280x2084, 619K)

It could be bad in the future especially if other software is written around it.

It's the modular nature of gnu/linux that allows it to constantly improve while software behemoths like windows or MacOS get worse.

Are you saying the scope creep and bloat that systemd already is can't be a little bit more bloated to not make it a bigger piece of shit

but it isn't a good reason, and whoever made that pic managed make himself look more like a sperg than poettering.

>name one better alternative
runit
>Linux
Linux is the most audited piece of software in the world. There are more eyes on it's source code at all times than any other program in the entire world.
OpenRC is buggier than SystemD, not by much though, and the bugs it has are not as egregious, but we shouldn't pretend it's perfect.

Attached: cgj5c0m1gmf21.jpg (1200x675, 100K)

I'm using gentoo on a shitbox and I don't want to add more compile time
/thread

factually wrong, mount is the utility to mount devices, I'm pretty sure efivars is read write right now in fucking openrc gentoo.
You retards blame systemd for stupid shit.

this

It's not gnu shepherd

>give me reasons for why systemd bad, but i won't accept them

You are a philosopher, Thrasymachus, I replied, and well know thatif you ask a person what numbers make up twelve, taking care to prohibithim whom you ask from answering twice six, or three times four, or sixtimes two, or four times three, 'for this sort of nonsense will not dofor me,' --then obviously, that is your way of putting the question, noone can answer you. But suppose that he were to retort, 'Thrasymachus,what do you mean? If one of these numbers which you interdict be the trueanswer to the question, am I falsely to say some other number which isnot the right one? --is that your meaning?' -How would you answerhim

>mount is the utility to mount devices
Not sure why that matters. efivarfs is not mounted by default. systemd mounts it so you can run systemctl reboot --firmware and end up in the UEFI setup utility. It wouldn't need to be mounted rw at all times for that, though.

>Tell me at least one good reason why SystemD is bad
The devs work at redhat, redhat gets money from the NSA, this means the devs of systemd are getting paid by the NSA and for sane people that's bad.

You're welcome, thread can be closed.

>systemd is the only system in existance that bricks mobos
>not systemds fault

fuck off, get a brain

Nice goalpost move you brainlet piece of shit

twitter.com/mjg59/status/693496443395399680
I'll take the word of a kernel dev over some anonymous nobody like you any day of the week

Good riddance!