[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Re: Bug#727708: Fsck SystemD and its developers and its users. GR to override this please.



On Tue, Feb 11, 2014 at 09:30:07PM +0400, Vitaliy Filippov wrote:
> >Here's a challenge then: Implement everything the journal does, without
> >using a binary format, and show us it's not only doable, but performs
> >similarly.
> >
> >I would first recommend you read up - and try! - what the journal has to
> >offer. It's not as simple as you make it out to be.
> 
> Given that Debian transitions to systemd - it seems an option to me. )
> 
> But first I'll try to disable it completely, of course. IMHO it's
> also a suitable solution.
> 
> I understand there's more functionality than you can build up only
> using regexes. The point is - I don't understand why an INIT SYSTEM
> (!!!!!) should depend on these, generally non-trivial, features.
The "INIT SYSTEM" not not. PID 1 doesn't really care, it simply tries
to log messages to a socket (or the kernel buffer depending on settings).
If you e.g. remove the socket, or hook up something different to read
from it, system (the init itself) wil be just as happy.

It's the accompanying tools (mostly systemctl) which extracts
information from journal files to give more information to the
admin. But this is a fairly loose coupling, and if systemctl doesn't
find any (pertinent) messages, it will just not print them.

Zbyszek


Reply to: