Mailinglist Archive: yast-devel (91 mails)

< Previous Next >
Re: [yast-devel] RFC: Yast Logging Format
  • From: Stefan Hundhammer <shundhammer@xxxxxxx>
  • Date: Thu, 21 Jan 2016 11:42:43 +0100
  • Message-id: <56A0B623.1060102@suse.de>
On 21.01.2016 10:26, Lukas Ocilka wrote:
There's a new feature in the feature tracking tool that requests Yast to
log in the same format as dmesg and journalctl.

Bad idea.

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
Business Case: Easier to analyse logs in bug reports.

Easier for whom? Certainly not for us. And it's us who this log is for.
If we need a customer log, by all means, yes, let's create one. But that would be a completely separate log that has nothing to do with our y2log.

We could for example duplicate log.info, log.error, log.warning and write that to such a customer log.

As a user, I'd also welcome a log with commands that were executed, files that were changed (or use a Git repo for them anyway?), but that's yet another level.

But our y2log is for us for debugging. If we need to comply with weird formats, we won't be able to do many things we are doing today any more, so we will no longer be able to maintain the product.

For example, look at the new format of the storage "target map" in current y2logs. Formatting this to be bug compatible with systemd would mean to get back the one-line format which is completely unusable (I spent many hours reformatting that stuff manually just to figure out what happened in bug situations).

Our y2log is our most important tool. It's not a playground for people who won't be responsible for debugging stuff.


So, bottom line: We might want to write an additional customer/user log, but our y2log is holy. Amen. ;-)


CU
--
Stefan Hundhammer <shundhammer@xxxxxxx>
YaST Developer

SUSE Linux GmbH
GF: Felix Imendörffer, Jane Smithard, Graham Norton; HRB 21284 (AG Nürnberg)
Maxfeldstr. 5, 90409 Nürnberg, Germany
--
To unsubscribe, e-mail: yast-devel+unsubscribe@xxxxxxxxxxxx
To contact the owner, e-mail: yast-devel+owner@xxxxxxxxxxxx

< Previous Next >
Follow Ups
References