[prev in list] [next in list] [prev in thread] [next in thread] 

List:       opensuse
Subject:    Re: [opensuse] Re: Why are systemd's logs stored as binaries?
From:       "Carlos E. R." <robin.listas () telefonica ! net>
Date:       2016-12-23 11:30:48
Message-ID: b56216b7-3044-eacc-529b-08028db1014c () telefonica ! net
[Download RAW message or body]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA256

On 2016-12-22 19:29, Greg Freemyer wrote:
> On Thu, Dec 22, 2016 at 11:58 AM, Anton Aylward 
> <opensuse@antonaylward.com> wrote:
>> On 12/22/2016 11:29 AM, Carlos E. R. wrote:


> But, what if I'm doing an examination of a server 5 years after
> the fact.  (I really do things like that on occasion.)
> 
> I haven't seen a spec for the journald binary format.  I haven't
> seen a commitment that journalctl from 2020 will have backward 
> compatibility to read 2016 journald logs.
> 
> I'm not saying those don't exist, but without that commitment at a 
> minimum systemd loses much of its value for me as an incident
> response responder.  And unfortunately I'm not normally part of the
> planning process for this.  I get called in when the incident is
> identified, not years earlier when the logging system is
> established.
> 
> I interpret Carlos's question to relate to that commitment.  It is
> a very important question.  I truly hope the commitment has been
> made, but to claim it is unimportant is simply wrong.

Yes, absolutely. I was thinking of that.

- -- 
Cheers / Saludos,

		Carlos E. R.

  (from 13.1 x86_64 "Bottle" (Minas Tirith))
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2.0.22 (GNU/Linux)

iF4EAREIAAYFAlhdCucACgkQja8UbcUWM1x0rwD/QiNHttIJLVsc/E7FbGShcRiG
uXUKnPCbHVRQXgNDuaEA/RyPgNhXpcNt05cA1cDASnGdn8MQyTjgGkiHXzFqhlkt
=YEV5
-----END PGP SIGNATURE-----

-- 
To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org
To contact the owner, e-mail: opensuse+owner@opensuse.org

[prev in list] [next in list] [prev in thread] [next in thread]