Bug 148701 - no /v/l/boot.msg if udev_log=info
Summary: no /v/l/boot.msg if udev_log=info
Status: RESOLVED WORKSFORME
Alias: None
Product: SUSE Linux 10.1
Classification: openSUSE
Component: Basesystem (show other bugs)
Version: Beta 3
Hardware: Other Other
: P5 - None : Normal (vote)
Target Milestone: ---
Assignee: Dr. Werner Fink
QA Contact: E-mail List
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2006-02-07 14:29 UTC by Christian Zoz
Modified: 2006-02-07 16:42 UTC (History)
0 users

See Also:
Found By: Other
Services Priority:
Business Priority:
Blocker: ---
Marketing QA Status: ---
IT Deployment: ---

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description Christian Zoz 2006-02-07 14:29:31 UTC 
I eneabled udev debug with /etc/udev/udev.conf:udev_log=info and rebootet. When booting finished there was no /var/log/boot.msg.

udev_log=info produces very much output at boottime. Might this be the reason?
Comment 1 Dr. Werner Fink 2006-02-07 15:01:26 UTC 
I don't know, but blogd uses a ringbuffer. IMHO the 65kB should be
enough for logging the first few seconds of the console output.

One reason could be that the blogd during boot time can not
write to /var/log/ or the /var/log/ was filled by an other
log file upto its limit.  The first write of the ringbuffer
is done in the boot.klog script by sending the signal SIGIO
to the running blogd.

Beside this the second blogd used during the runlevel changes
or from boot to initial runlevel should be able to write to
/var/log/.  If not there is a) no blogd or b) no writable
/var/log/ directory.
Comment 2 Christian Zoz 2006-02-07 15:41:06 UTC 
It was another problem: aparmor

I do now get at least some messages from udev (170 out of over 1000 events).
Comment 3 Dr. Werner Fink 2006-02-07 15:52:10 UTC 
In other words: it is not a bug of blogd?
Comment 4 Christian Zoz 2006-02-07 16:41:09 UTC 
no
Comment 5 Dr. Werner Fink 2006-02-07 16:42:42 UTC 
closed