Bug 527320

Summary:	sys-fs/udev-init-scripts - /etc/conf.d/udev /etc/init.d/udev should set `udevadm trigger' verbosity
Product:	Gentoo Linux	Reporter:	Jeroen Roovers (RETIRED) <jer>
Component:	[OLD] Core system	Assignee:	Gentoo systemd Team <systemd>
Status:	RESOLVED WONTFIX
Severity:	normal
Priority:	Normal
Version:	unspecified
Hardware:	All
OS:	Linux
Whiteboard:
Package list:		Runtime testing required:	---

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?

Comment 3 Mike Gilbert gentoo-dev

2023-09-18 01:13:23 UTC

Closing due to lack of response.