Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

ci(suse.conf.example): change log levels #370

Open
wants to merge 1 commit into
base: SUSE/059
Choose a base branch
from

Conversation

aafeijoo-suse
Copy link
Collaborator

Reduce default standard log verbosity from info to warning, and increase syslog verbosity from none to info.

This is just a proposal to adjust the log verbosity (IMHO excessive). Suggestions are welcome.

CC @mwilck @fbuihuu

Reduce default standard log verbosity from `info` to `warning`, and increase
syslog verbosity from none to `info`.
@aafeijoo-suse
Copy link
Collaborator Author

FTR, with this change successful initrd builds are no longer logged by zypper, only appear on the journal.

@tblume
Copy link
Collaborator

tblume commented Sep 16, 2024

The idea is good, but I'm afraid we might get resistance due to backward compatibility, at least for SLES/LEAP.
I guess this change will have to stay in tumbleweed for a while until people get used to the new log output.

@mwilck
Copy link

mwilck commented Sep 16, 2024

I disagree. I believe the vast majority of users will rejoice about this change.
Moreover, it's very easily undone by changing the loglevel back to the previous value.

@aafeijoo-suse
Copy link
Collaborator Author

The idea is good, but I'm afraid we might get resistance due to backward compatibility, at least for SLES/LEAP.

I wasn't thinking about backporting this for SLE-15, but for Tumbleweed and new products there should not be any problem IMO. I've been hearing the same complaint about dracut being too verbose over the years, so we should change this at some point.

@tblume
Copy link
Collaborator

tblume commented Sep 16, 2024

The idea is good, but I'm afraid we might get resistance due to backward compatibility, at least for SLES/LEAP.

I wasn't thinking about backporting this for SLE-15, but for Tumbleweed and new products there should not be any problem IMO. I've been hearing the same complaint about dracut being too verbose over the years, so we should change this at some point.

Agreed, still I think we should do a feature request for SLFO, just to be on the safe side.

Copy link
Collaborator

@tblume tblume left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM

@aafeijoo-suse
Copy link
Collaborator Author

Agreed, still I think we should do a feature request for SLFO, just to be on the safe side.

Created jsc#PED-10809

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants