Gentoo Websites Logo
Go to: Gentoo Home Documentation Forums Lists Bugs Planet Store Wiki Get Gentoo!
Bug 527320 - sys-fs/udev-init-scripts - /etc/conf.d/udev /etc/init.d/udev should set `udevadm trigger' verbosity
Summary: sys-fs/udev-init-scripts - /etc/conf.d/udev /etc/init.d/udev should set `udev...
Alias: None
Product: Gentoo Linux
Classification: Unclassified
Component: [OLD] Core system (show other bugs)
Hardware: All Linux
: Normal normal (vote)
Assignee: Gentoo systemd Team
Depends on:
Reported: 2014-10-29 09:58 UTC by Jeroen Roovers (RETIRED)
Modified: 2021-08-09 15:16 UTC (History)
0 users

See Also:
Package list:
Runtime testing required: ---


Note You need to log in before you can comment on or make changes to this bug.
Description Jeroen Roovers (RETIRED) gentoo-dev 2014-10-29 09:58:20 UTC
Starting /etc/init.d/udev can take more than a few seconds to finish. When it fails it remains silent and often hangs - the reasons are usually beyond its control.

Currently the only way to find out what failed is to start the system interactively and/or figuring out what went wrong by reading dmesg output.

I think adding --verbose to the `udevadm trigger' calls in populate_dev() might help resolve issues much easier.
Comment 1 Jeroen Roovers (RETIRED) gentoo-dev 2014-10-29 10:01:33 UTC
udevadm trigger --verbose is /really/ verbose - it prints out a complete list, sadly.
Comment 2 William Hubbs gentoo-dev 2014-12-03 17:09:48 UTC
You are correct, adding --verbose by default to the udevadm trigger
commands would make for a very verbose boot.

What I could do is give you a way to add it yourself if you want it, for
example a variable like trigger_extra_opts in /etc/conf.d/udev-trigger
which would then be passed to the udevadm trigger commands. By default
it would be empty because of the amount of output the --verbose option
would generate.

What do you think about this idea?