[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.



It is of course well-known that systemd developers like to make their
life more complicated and love to implement binary formats instead of
writing simple text parsers, just for the sake of having fun programming
them, and absolutely not because they need things like indexing.

The same goes for relational databases developers, for example. How
silly of them all.

1) If you really need a binary index, it could be initially put in a separate file. 2) Binary index isn't needed at all if you just want to print output of a service - you can just put output of each unit to its own log file and just tail it. 3) If you don't want to print only last X lines, but want to print full output of a service since last start - you can remember the previous log position in the service state structure. 4) At a first glance I don't see any _real_ index (i.e. btree) implementation in systemd journal, so I assume it still does fullscans to print logs for a service - am I correct? 5) After all, I don't see why writing 1 regexp is a hard task. And it won't be really slower because of (4).

DBMS is an incorrect example because DBMS is originally _meant_ to store and query structured data in different formats.

--
With best regards,
  Vitaliy Filippov


Reply to: