How is this bad? Does anybody bother reading the posts they reply to anymore?
Fuck, given that you have said "the defaults are fine" and "the defaults are whatever the distro decides on" maybe you should read the posts you are writing
"[ KDE ] should be the default because it's highly configurable" but "the defaults are fine, and there's nothing forcing you to configure it differently".
Ok, if you say so.
How will the defaults being what you want stop people playing with them?
Examples of systemd breaking the kernel include the "debug" logging option
Which no more broke the kernel than any other process writing a lot of log messages.
and the inevitable failures of such a complex weave of components killing PID 1
How scary.
Unfortunately, "running syslogd in parallel" doesn't work well as new daemons or services are compiled for one or the other.
Anything written to syslog is received by journald. Anything received by journald can be forwarded to rsyslogd. Where's the problem?
And yes, systemd is trying to replace "su". See the comments by systemd's core author, Leonart Pottering
You mean the bit where he says he's not going to change the behaviour of "su" to make it do things it wasn't supposed to, but for the people who need that he's made a new command? You'd rather he hacked "su" to do what some systemd users wanted?
Why on earth are you bringing the TSCOG mess? How is that supposed to be relevant? Oh, you mean LP's little joke: "I understand this is confusing and unexpected, but well, that's UNIX..." In that sense then he's right, Linux is emulating UNIX and it's "su" command is supposed to do what the "su" command on a UNIX system would do. Any UNIX programmer understands that from a programmers point of view Linux is a UNIX. Let's leave the lawyers and other trolls out of the discussion.
[Service] Type=forking
[...] ExecStart=/usr/local/bin/mongod $OPTIONS run
and a program (mongod) that prints an error message to stderr then exits nothing will be found in the journal.
It's easy to try, and it turns out to be not true.
It is true that, since the unit is marked "Type=forking" then if mongod exits with an error after the fork then "sysemctl start" won't show the error code (neither will the sysvinit init.d script). "systemctl status" will, of course, show the error.
No, [ KDE ] should be the default because it's highly configurable.
Frankly that's one reason I don't use it and don't want my users to use it. The amount of time people waste configuring crap instead of using it prevents any work getting done.
Uhh, that isn't mentioned on the man page for systemd on CentOS or Fedora. Also, I just tried it, and that does not work.
$ man systemd.service [...] OPTIONS
Service files must include a "[Service]" section, which carries
information about the service and the process it supervises. [...]
Type=
Configures the process start-up type for this service unit. One of
simple, forking, oneshot, dbus, notify or idle. [...]
if the quantity of carbonic acid increases in geometric progression, the augmentation of the temperature will increase nearly in arithmetic progression.
That's much better than systemd where messages typically don't make it to the journal.
with systemd the only times messages don't make it to the journal is when either: 1. the unit file explicitly says to send the messages to the console or 2. an init script is being used and it ends the messages somewhere else
in both cases systemd does exactly what sysvinit does.
Slashdot Mirror
Yup, the real actual threat of global thermonuclear war has turned into an idiot in a train who has his guns taken off him by some passengers.
OOP:
In an OOP world every sock would have an attached washing machine.
Sounds like you are still stuck in the 70s to this day.
Ah, the 1970's where nobody had ever heard of OOP.
Simula? Smalltalk? Never heard of 'em.
So FreeBSD, which ships gnome, uses systemd?
Yeah, I was wrong about that -- misread the El Reg article. What a maroon.
No, it was due to the earth sample being aged in a cask, while the ISS sample was in a glass container with some wood savings.
How is this bad? Does anybody bother reading the posts they reply to anymore?
Fuck, given that you have said "the defaults are fine" and "the defaults are whatever the distro decides on" maybe you should read the posts you are writing
Why would a lot of code need to be "fixed" just because someone anally retentive wants deterministic builds?
Uh, because some anally retentive person wants deterministic builds? Did you RTFS?
No elaborate troubleshooting is necessary, I just felt like checking out the extraordinary claim of the AC above.
And it turned out that he was full of shit, as usual.
You do know that you sound like a crazy person, don't you?
"[ KDE ] should be the default because it's highly configurable" but "the defaults are fine, and there's nothing forcing you to configure it differently".
Ok, if you say so.
How will the defaults being what you want stop people playing with them?
Examples of systemd breaking the kernel include the "debug" logging option
Which no more broke the kernel than any other process writing a lot of log messages.
and the inevitable failures of such a complex weave of components killing PID 1
How scary.
Unfortunately, "running syslogd in parallel" doesn't work well as new daemons or services are compiled for one or the other.
Anything written to syslog is received by journald. Anything received by journald can be forwarded to rsyslogd. Where's the problem?
And yes, systemd is trying to replace "su". See the comments by systemd's core author, Leonart Pottering
You mean the bit where he says he's not going to change the behaviour of "su" to make it do things it wasn't supposed to, but for the people who need that he's made a new command? You'd rather he hacked "su" to do what some systemd users wanted?
Why on earth are you bringing the TSCOG mess? How is that supposed to be relevant? Oh, you mean LP's little joke: "I understand this is confusing and unexpected, but well, that's UNIX..." In that sense then he's right, Linux is emulating UNIX and it's "su" command is supposed to do what the "su" command on a UNIX system would do. Any UNIX programmer understands that from a programmers point of view Linux is a UNIX. Let's leave the lawyers and other trolls out of the discussion.
Who said it was easier? The contention was that it was impossible with systemd.
And, of course, your grep will work if rsyslogd is installed and you look in the right log:
P.S. I assume you meant "tail | grep" not "grep | tail" !
The assertion is that with a unit file that says:
and a program (mongod) that prints an error message to stderr then exits nothing will be found in the journal.
It's easy to try, and it turns out to be not true.
It is true that, since the unit is marked "Type=forking" then if mongod exits with an error after the fork then "sysemctl start" won't show the error code (neither will the sysvinit init.d script). "systemctl status" will, of course, show the error.
So, the AC above is lying.
No, [ KDE ] should be the default because it's highly configurable.
Frankly that's one reason I don't use it and don't want my users to use it. The amount of time people waste configuring crap instead of using it prevents any work getting done.
But udev doesn't depend on systemd, so your slippery slope is not very slippery.
systemd has already broken the kernel repeatedly
"Broke the kernel"? Rubbish. "Repeatedly"? Rubbish.
[broke] a decade of log collection and analysis tools that I personally use
So just run syslogd. What's your problem?
and now it's trying to replace "su"
No it isn't.
You get all your information from trolls, makes you look like a troll yourself.
Uhh, that isn't mentioned on the man page for systemd on CentOS or Fedora. Also, I just tried it, and that does not work.
It's the wrong solution to the "problem" however.
Why do you bother lying like this? It just brings discredit on people who dislike systemd.
Yes, how dare he develop software that people can use if they want to, the bastard.
If he'd been Spanish maybe his blog would have been "Pid Uno". Would that freak you out?
How long have we been talking about AGW?
Almost 120 years now.
-- Arrhenius, 1896.
That's much better than systemd where messages typically don't make it to the journal.
with systemd the only times messages don't make it to the journal is when either:
1. the unit file explicitly says to send the messages to the console
or
2. an init script is being used and it ends the messages somewhere else
in both cases systemd does exactly what sysvinit does.
(sorry, I forgot to add why -- the police asked the government to stop it as they had no more room to put all the stupid cardbord files).