On Thu, May 02, Roberto Angelino wrote:
I have a customer who is asking if it's OK to set Y2DEBUG=1 all the time:
When we encounter SLES media problem, one of the first things SuSE engineers ask us to do is reproduce with Y2DEBUG=1 on
Do they? I am surprised about that. I cannot remember to have requested logs with Y2DEBUG set at all the last some years. In fact since I do sometimes get logs with Y2DEBUG=1 (no idea why), I even use scripts to throw away the added junk of Y2DEBUG to get usable log files. Maybe this is simply a ballot point at NCC? If yes, maybe we should try to remove that. What about others? Do we really regularly need logs with Y2DEBUG=1?
the kernel commandline. We were thinking about always having this media feature enabled going forward. Can we ask SuSE engineers if there is any cause for concern in doing this?
The biggest problem is that logs may get overwritten round-robin-wise if they tend to get too big. Especially in storage area this can be fatal, when a problem possibly related to storage (e.g. bootloader setup, fstab entries) show up at end of install and log of storage setup (which happens at begin of install) is already overwritten. Bye, Thomas Fehr -- Thomas Fehr, SuSE Linux Products GmbH, Maxfeldstr. 5, 90409 Nuernberg, Germany GF: Jeff Hawn, Jennifer Guild, Felix Imendörffer, HRB 16746 (AG Nürnberg) Tel: +49-911-74053-0, Fax: +49-911-74053-482, Email: fehr@suse.de GPG public key available. -- To unsubscribe, e-mail: yast-devel+unsubscribe@opensuse.org To contact the owner, e-mail: yast-devel+owner@opensuse.org