On 02/03/2018 09:30 PM, Todd Zullinger wrote:
Samuel Sieb wrote:
How is it not useful? I'm happy to be aware of that part of the
transaction. It would certainly be more useful if there was some indication
of what specifically it was for.
IMO, it's not useful because it tells the user nothing about
what script is actually running.
What useful information is included in:
Running as unit: run-re2635381e8fe44a6aad4926eddab6961.service
It lets me know that something else was run, just like there's a line
saying that it's running a scriptlet for package whatever. As I
mentioned, I would much prefer that there was some part of that line
that said what the unit is for, but at least with that line I know that
it's happening and I can check the logs if necessary.
All I see in the case of the man-db-cache-update scriptlet
is that the typical >/dev/null was missed when it was
converted to use systemd-run. The scriptlet before was:
MAN_NO_LOCALE_WARNING=1 /usr/bin/mandb -q
That is silent by design. The MAN_NO_LOCALE_WARNING=1 was
This being silent ended up being a problem. mandb took a long time to
run and there was no explanation on why the dnf transaction appeared to
be hung for several minutes. It would have been good if there had been
some output saying that mandb was being run. Sure you might be able to
switch consoles and run "ps" if you know about that, but this would have
been easier.
_______________________________________________
users mailing list -- users@xxxxxxxxxxxxxxxxxxxxxxx
To unsubscribe send an email to users-leave@xxxxxxxxxxxxxxxxxxxxxxx
