Gentoo Websites Logo
Go to: Gentoo Home Documentation Forums Lists Bugs Planet Store Wiki Get Gentoo!
Bug 376727 - sys-apps/openrc-0.8.3 rc.log will not capture udevadm errors at early bootup stage
Summary: sys-apps/openrc-0.8.3 rc.log will not capture udevadm errors at early bootup ...
Status: RESOLVED INVALID
Alias: None
Product: Gentoo Linux
Classification: Unclassified
Component: [OLD] baselayout (show other bugs)
Hardware: All Linux
: Normal normal (vote)
Assignee: OpenRC Team
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2011-07-28 13:05 UTC by Vladimir Berezhnoy
Modified: 2011-07-31 19:58 UTC (History)
2 users (show)

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


Attachments
sample udev rule (99-printer.rules,111 bytes, text/plain)
2011-07-28 13:06 UTC, Vladimir Berezhnoy
Details

Note You need to log in before you can comment on or make changes to this bug.
Description Vladimir Berezhnoy 2011-07-28 13:05:21 UTC
This is what I have in rc.log

 * Populating /dev with existing devices through uevents ...
 [ ok ]
 * Waiting for uevents to be processed ...
 [ ok ]
 * Mounting /dev/shm ...
 [ ok ]


But during boot I see three errors after "Populating /dev with existing devices through uevents" and after "Waiting for uevents to be processed:" from udevd claiming that file which start with /usr are not available.

Later I see errors from other services, which are captured in log correctly.

Reproducible: Always

Steps to Reproduce:
1. install either media-sound/alsa-utils-1.0.24.2-r1 or net-wireless/bluez-4.94-r1
2. use separate /usr partition
3. enable logging in rc.conf 
4. Errors will be produced during early bootup from udevd, but none of them will be captured in rc.log
Comment 1 Vladimir Berezhnoy 2011-07-28 13:06:46 UTC
Created attachment 281263 [details]
sample udev rule

Another udev rule which will produce errors during bootup, but none of them are captured in rc.log
Comment 2 William Hubbs gentoo-dev 2011-07-31 19:58:22 UTC
Please note the following comments in rc.conf:

# rc_logger launches a logging daemon to log the entire rc process to
# /var/log/rc.log
# NOTE: Linux systems require the devfs service to be started before
# logging can take place and as such cannot log the sysinit runlevel.

Udev is currently started in the sysinit runlevel, so it cannot be
logged. The errors you are describing sound like they may be fixed by
bug #364235, so you might want to watch that bug.