|
Bugzilla – Full Text Bug Listing |
| Summary: | no /v/l/boot.msg if udev_log=info | ||
|---|---|---|---|
| Product: | [openSUSE] SUSE Linux 10.1 | Reporter: | Christian Zoz <zoz> |
| Component: | Basesystem | Assignee: | Dr. Werner Fink <werner> |
| Status: | RESOLVED WORKSFORME | QA Contact: | E-mail List <qa-bugs> |
| Severity: | Normal | ||
| Priority: | P5 - None | ||
| Version: | Beta 3 | ||
| Target Milestone: | --- | ||
| Hardware: | Other | ||
| OS: | Other | ||
| Whiteboard: | |||
| Found By: | Other | Services Priority: | |
| Business Priority: | Blocker: | --- | |
| Marketing QA Status: | --- | IT Deployment: | --- |
|
Description
Christian Zoz
2006-02-07 14:29:31 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. It was another problem: aparmor I do now get at least some messages from udev (170 out of over 1000 events). In other words: it is not a bug of blogd? no closed |