Bugzilla will be upgraded to version 5.0. The upgrade date is tentatively scheduled for 2 December 2018, pending final testing and feedback.
Bug 154329 - sysreport generates incomplete modinfo output
sysreport generates incomplete modinfo output
Product: Red Hat Enterprise Linux 4
Classification: Red Hat
Component: sysreport (Show other bugs)
All Linux
medium Severity low
: ---
: ---
Assigned To: Ngo Than
Ben Levenson
Depends On:
  Show dependency treegraph
Reported: 2005-04-09 23:08 EDT by Stephen Gardner
Modified: 2007-11-30 17:07 EST (History)
0 users

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Last Closed: 2005-06-21 07:46:33 EDT
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

Attachments (Terms of Use)

  None (edit)
Description Stephen Gardner 2005-04-09 23:08:07 EDT
Description of problem:
sysreport uses the  catifexec  function to capture the output from the modinfo
command to a  modinfo  file. However  modinfo  is called multiple times from
within a for loop, once for each kernel module loaded, and as  catifexec  uses
">" the modinfo output file is overwritten with each successive repetition. The
sysreport modinfo file therefore only contains the information from the last
modinfo call (ie. the last module from the lsmod list it uses).

Version-Release number of selected component (if applicable):
+   sysreport-1.3.14-1   taken from RHEL4-U1-beta
Comment 1 Stephen Gardner 2005-04-09 23:11:18 EDT
Not entirely sure how the Summary got so big... very odd.
Comment 2 Ngo Than 2005-05-09 10:52:21 EDT
it's now fixed in CVS. The sysreport-1.3.15-1 will include this fix. I will build
it in RHEL4-U2 tree this week. Thanls for report
Comment 3 Jay Turner 2005-06-21 07:46:33 EDT
An advisory has been issued which should help the problem
described in this bug report. This report is therefore being
closed with a resolution of ERRATA. For more information
on the solution and/or where to find the updated files,
please follow the link below. You may reopen this bug report
if the solution does not work for you.


Note You need to log in before you can comment on or make changes to this bug.