I can find the bug in an overly complex init script, yes. If they had a simple systemd unit there would be no bug to find.
(I found the bug in the init script in 10 minutes, the GP claims it took his crew of elite developers and Redhat support a whole day. Either he is an idiot or he is lying -- I suspect both).
Comment needs funny+insightful, slashidiots give troll...
Hundreds of DOS ini files, having to compile things instead of just modding a script,
"having to compile things"? Like what for example?
Now, personally, I'm willing to try it out on my laptop for awhile, and maybe, just maybe, I will consider deploying this in servers, in like 6 months after daily use by myself and my alternate. Otherwise we'll keep using 14.10 for now.
You use Ubuntu on servers?
Neither. Why would you imagine it would?
Why not just use Debian?
So you suffered through Unity, but systemd is what turns you away? Huh.
No, he suffered through upstart and systemd is what turns him away?
Maybe mr smug, you can tell me where on earth the ACPI events from the sleep key are going and why SystemD refuses to pass them on anywhere sensible.
Works for me. Maybe you could describe your environment in more detail?
Another moderation that demonstrates the insanity of the anti-systemd trolls.
Even if you hate systemd for valid reasons, what kind of moron is going to mod up a comment that is a straight out lie just because it is anti-systemd?
Well, that was a failure then, in comparison to sysvinit systemd is limpid.
I think this is the same problem that stumped Red Hat's support for a while when we first upgraded to 7. MongoDB refuses to start after an unclean shutdown. It detects that by placing its PID in a file named mongod.lock on start and then clearing the PID on clean shutdown. When you start MongoDB with the lock file in place, it gives you an immediate and clear error message on stderr that this is the problem. When starting with systemd, because it swallows stderr and syslog messages, there is no indication whatsoever what is causing it to not start. There is nothing in the journal or the console.
And, as I've already pointed out: http://slashdot.org/comments.pl?sid=6953777&cid=49050025
This is a bug in the mongodb init script, it directs stderr to
If the mongodb init script sends stderr to
was of course deleted and ignored:
And that is the even bigger problem with systemd.
No, it's a big problem with your insanity.
This bug, since it doesn't exist, was never reported.
What if your name is Clinton?
Not sure what civilization you are referring to, but here in the good ole' US-of-A everyone is primarily concerned about buying beer, their heroin addiction, and gay marriage.
The price of admission for us geeky folks to support the infrastructure responsible for the bread-and-circuses is that they have to throw a little bone (less than 1% of GDP) to things we think are cool. Otherwise we would all be cyberterrorists and commies.
You have a message from the operator.
