Keep on backpedalling.

But I thought system logs never got corrupted! You do realize that system logs aren't flushed to disk line by line in most cases right? That would be a huge amount of incredibly slow disk IO and seeks. That "half line" can be the head of dozens of entries. Which again...when you also have to factor in the speed considerations for the relative size of each the messages...

Yeah no I didn't. I said "Debian".

So in addition to having no clue, you also apparently can't read. Which well, I guess one does explain the other.

Fabricating info? Then I guess this doesn't exist?

There are Debian packages for systemd-init. There are Ubuntu packages.

So we return to my original opinion...

systemd can launch shell scripts and you can turn off all the other features involved there. So yes, it has been handled - the fallback is you write a shell script, like you already do, that does this manually.

Though again I ask: what reports? Where? I am specifically curious of cases where systemd breaks, because I am running it right now and trying to evaluate it for using it on other systems in the future. Vague concerns do not help that.

Yes because I'm sure the literally microseconds of lag (I mean maybe, there's a lot of assumptions in that statement) is a problem compared to, I don't know, the 100s of milliseconds it takes to flush anything to disk. Presuming it gets there, because if the system goes down, it's unlikely anything gets written out of any memory buffer.

Then of course there's the byte overhead of all those characters rather then concise binary files, so there's a bandwidth cost too.

But it's pretty obvious you don't actually know what you're talking about and are just spreading FUD.

Well good news, this is the default, at least on Debian. In fact Debian doesn't even store journalctl logs, it fowards then straight through to rsyslog.

Of course, if you and literally every other Anon. Coward in this thread of posts knew what they were talking about, then it wouldn't exist.

The "anti-systemd" brigade seems to consist of a lot of people who have absolutely no idea what they're doing, let alone any idea of how Linux actually works.

If it wasn't booting, then there is some sort of error message. Or no error message just a hang maybe! But no, that's never what anyone feels is "worth" mentioning. Just "it broke". I'm sure in debugging init script problems they would've supplied exactly the same information. Or you know, not, because it's extremely unlikely their system was locking up completely.

It also has the great property of letting you install partial configuration overrides per-file by dropping a file in a subdirectory /etc/systemd named after the file you're editing.

Solving the problem once, in the init system, is smarter then having to solve it every single time in every single init script (or you know, it may do anything from not work to stall the entire boot).

And "journalctl" works just fine for systemd, what's your point?

Plus bonus: you can easily tail all the logs on the system with "journalctl -f" and you can of course pipe that output into grep or whatever else you want.

So again, what's your point?

Indeed. People keep saying this and never what they were.

Blood tests don't detect Ebola reliably before symptoms manifest.

I pay $8 a month and get a gig of data. I do a lot of browsing on my phone. For example I'm posting this from it while on a bus.

Also because there's little to study, it's hard to test a vaccine, and its also downright dangerous to study. Mundane pathogens that nonetheless kill a lot of people have the delightful property of being almost completely survivable if you contract them accidentally in a research setting.