Not to mention I imagine Poettering is going to get a stern talking to because RHEL7 is patched by default to allow these kinds of usernames (as mentioned in that thread) and you can imagine that there's some kind of proprietary shit out there or noisy customer that uses a name like this, so it'll be fixed at some point. But, again, not that big of a deal.
CVE-2017-9445 Systemd DNS
I'm GenZ and I know this (Upstart, Openrc or SysV btw). Your generation isn't an excuse, just ask the question without trying to find excuses for why you don't have this knowledge.
Do I need to link the amount of catastrophic bugs in the Upstart bug tracker? The cripple even ran into one when NT Technology forced him to run Ubanto on the servers. It's dogshit.
Wow, more dogshit RC scripts that can't even keep track of the real state of a daemon or child processes, complete with the racey behavior that's been hacked around for decades.
lol
I already went over daemontools above. systemd was the only option. You never see UNIX fags complain about Solaris SMF or old Unix greybeards complain about launchd on OS X. It's because they're not as autistic as the NEETs here, of course.
Oh, the only thing that Upstart was good at was a SysV shim, and systemd is better at it especially for obscure compatibility. Aside from that, Upstart jobs were catastrophically broken to the core when it came to anything besides babby's first upstart jobs, one of the developers admitting that it would require a lot of rewriting, so of course it won the fight.
Not to mention the useless cgroups functionality seemingly implemented the way it was because they wanted to be as different from systemd as possible. There's no other way to explain that.
as a sysadmin, i've had the opposite experience.
i ended up switching my personal machines to FreeBSD while my developer colleagues have been slobbering all over Lennart's knob.
No, it was more Spotify and anyone else who wasn't a fucking retard on the mailing list who chimed in.
Anything was better than Upstart, Red Hat even went through the systemd switch from Upstart because of the problems Upstart had, and no one wanted RC script hacks. Dion't pretend you know what you're talking about, because you don/t.
-Massive Shilling
-Backed by Red Hat
rustcuck leave. this is not your home.
That is a feature, not a bug.
It does it for good reasons, like everything else sane. The point is that systemd can do it no problem, and gives me easy to use cgroups administration of services. I have several bits of critical legacy proprietary cruft that double forks, and even if I didn't why should I have to modify every piece of shit that doesn't have an option to run as foreground?