Bug 23481
Summary: | 'wait for klogd to hit syslog' doesn't (minilog) | ||
---|---|---|---|
Product: | [Retired] Red Hat Raw Hide | Reporter: | Andrew Bartlett <abartlet> |
Component: | initscripts | Assignee: | Bill Nottingham <notting> |
Status: | CLOSED NOTABUG | QA Contact: | David Lawrence <dkl> |
Severity: | medium | Docs Contact: | |
Priority: | low | ||
Version: | 1.0 | CC: | rvokal |
Target Milestone: | --- | ||
Target Release: | --- | ||
Hardware: | i386 | ||
OS: | Linux | ||
Whiteboard: | |||
Fixed In Version: | Doc Type: | Bug Fix | |
Doc Text: | Story Points: | --- | |
Clone Of: | Environment: | ||
Last Closed: | 2001-01-06 11:55:16 UTC | Type: | --- |
Regression: | --- | Mount Type: | --- |
Documentation: | --- | CRM: | |
Verified Versions: | Category: | --- | |
oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
Cloudforms Team: | --- | Target Upstream Version: | |
Embargoed: |
Description
Andrew Bartlett
2001-01-06 11:55:13 UTC
Hm, it's really just a timing issue. Not something we can truly enforce ordering on (and, in any case, the kernel messages and the syslog messages are intermingled in timing, so unless we start having the kernel timestamp them and have syslogd sort them they won't be in order.) I'll change it to sleep(2), but that may not necessarily help. Didn't particulary help, but thanks for your efforts. Another idea: Could rc.sysint dump dmesg into minilog, therefore getting it to the top of the pile? Anyway, there are much more important things to worry about than the prettyness (or otherwise) of logfiles. |