From anti-systemd to pro-systemd in the shortest time

Posted Jan 31, 2014 2:46 UTC (Fri) by dlang (guest, #313)
In reply to: From anti-systemd to pro-systemd in the shortest time by zuki
Parent article: This week in "As the Technical Committee Turns"

well, it works without a problem before systemd inserts itself into the process, replacing the stuff that was there before.

so yes, it is a systemd related problem

it's the systemd developer's fault because they mandate that if you use systemd, systemd will do this.

This isn't a kernel issue, this is sticking strictly with userspace components.

From anti-systemd to pro-systemd in the shortest time

Posted Jan 31, 2014 3:18 UTC (Fri) by dlang (guest, #313) [Link] (4 responses)

for what it's worth, we do know the exact cause of the problem, it's not a mystery and it makes perfect sense.

It's also something that a desktop user is almost never going to run into, and it is a result of physics, not sloppy programming or something like that. The only way to avoid the problem is to sidestep the mandatory systemd component.

From anti-systemd to pro-systemd in the shortest time

Posted Jan 31, 2014 3:24 UTC (Fri) by Cyberax (✭ supporter ✭, #52523) [Link]

>the mandatory systemd component.
Which one? Automount? Does it have something to do with network latency?

From anti-systemd to pro-systemd in the shortest time

Posted Jan 31, 2014 5:37 UTC (Fri) by raven667 (subscriber, #5198) [Link]

I'm a little bit annoyed by your lack of detail but if there is a bug report here then I'd love to see it get fixed, which is going to require some technical detail, hopefully not giving away any proprietary secrets.

From anti-systemd to pro-systemd in the shortest time

Posted Jan 31, 2014 19:07 UTC (Fri) by jspaleta (subscriber, #50639) [Link] (1 responses)

I take it this is a bit of proprietary code that none of the people discussing this of here will ever get to examine directly?

-jef

From anti-systemd to pro-systemd in the shortest time

Posted Jan 31, 2014 23:41 UTC (Fri) by dlang (guest, #313) [Link]

as you can see from the final details, no it's not proprietary code, it's a problem that affects anything that generates a large volume of logs.