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

eye of cyclon animation / verbose mode no longer shown for long running tasks #17157

Open
mbiebl opened this issue Sep 24, 2020 · 3 comments
Open

Comments

@mbiebl
Copy link
Contributor

mbiebl commented Sep 24, 2020

I was recently investigating, why I no longer got the eye-of-cylon animation / verbose mode when long running tasks during boot happened.
Turns out this is a regression that happened because of 0d066dd.
The distros I know, setup the boot process to add quiet to the kernel command line (at least Debian/Ubuntu and Fedora) by default. This is not an explicit user choice!
They now no longer get any feedback whatsoever for long running tasks, which is a bad idea.
Imho, quiet should imply systemd.show-status=auto as before and if a user wants to have a truly silent backup, this has to be an explicit choice.

Please consider reverting this change in behavior

@mbiebl mbiebl added the regression ⚠️ A bug in something that used to work correctly and broke through some recent commit label Sep 24, 2020
@mbiebl
Copy link
Contributor Author

mbiebl commented Sep 24, 2020

Let me add here that the auto mode is extremely helpful for users to see what's going on. The errors-only mode should only be left for users who explicitly configured it that way and know what that means.

@poettering poettering added this to the v247 milestone Sep 25, 2020
@keszybz keszybz added needs-discussion 🤔 and removed regression ⚠️ A bug in something that used to work correctly and broke through some recent commit labels Oct 5, 2020
@keszybz
Copy link
Member

keszybz commented Oct 5, 2020

It's not a "regression" — it's a deliberate change in behaviour. I still think the change is appropriate: most users simply don't care about the fact that systemd-hwdb.service was executed during the boot and took 6.2 seconds to finish. Even if this did happen, why should they get a transcript of other services which were started later? Pretty much everybody nowadays wants to have a flicker-free boot straight into the graphical environment. Spewing a hundred lines of generally boring and unrelevant stuff on the screen just because something was a bit slow is not useful.

Granted, there are users who like to see the details. Those users shouldn't put quiet on their command line. "quiet" means quiet, and with this change, we actually honour the intent of that setting.

@poettering
Copy link
Member

ok, let's drop the milestone then, as this is not clear cut

@poettering poettering removed this from the v247 milestone Oct 8, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Development

No branches or pull requests

3 participants