On Thu, 20 Feb 2014 15:37:09 -0800
Michael Higgins <li...@evolone.org> wrote:


> Okay, I'll go re-wire my tin hat now. Hope someone found this amusing.

One other thought I'd has was, well, as long as systemd doesn't, like,
implement some kind of net protocol, so to make it possible to ship
logs from systemdjournalcontrol. 

I mean, so what if then it just sits there doing its job, more or less.
You can even offload the job to your favourite logger, and it just sits
there, pretty much inoffensively in the pid 1 family.

Then I read this:

"I am curently working on getting log syncing via both a PUSH and PULL
model done. This will be based one existing protocols and standards as
much as we can (SSH or HTTP/HTTPS as transport, and JSON and more as
payload), and is flexible for others to hook into. For example, I think
it would be cool if greylog2 and similar software would just pull the
data out of the journal on its own, simply via HTTP/JSON. We make
everything available to make this smooth, i.e. we provide clients with
stable cursors which they can use to restart operation."

So, I don't know. That 'journalctl' seems to be really just a front-end
to some routines actuall coded in sytemd. So, I guess, windows all over
again? Really, a net protocol at that level? I'm sure there's no way to
exploit that.

What I do know is, that if any point I work again in IT, it will just
be part of "the way it is done", for the same reasons most shops don't
use Gentoo, for example. No one will blame you for using whatever, if
pretty much everyone else does so too. Plus, if there's some massive
codebase with a flaw causing a security breach, you're not alone.

But, seriously, flawed (carnivorous or nefarious) by design does seem to
be the upshot here, the more I read about the design decisions.

I don't think I've presented any compelling argument against anyone
else using it, per se, more than questioning the logic of it becoming
ubiquitous. It does seem to solve a lot of "real world" problems, in
one way, or another.

And I'm done looking at it, I think, and will leave it to others to
take my notes with the grains of salt required. For me, I don't really
have a need for what it offers, nor a "real world" need to worry about
possible implications of its design or rate of adoption.

Cheers,

> Cheers,
> 
> - mykhyggz
> 


Reply via email to