Note: This is a beta release of Red Hat Bugzilla 5.0. The data contained within is a snapshot of the live data so any changes you make will not be reflected in the production Bugzilla. Also email is disabled so feel free to test any aspect of the site that you want. File any problems you find or give feedback here.
Bug 77541 - sendmail config looked for inwrong place
Summary: sendmail config looked for inwrong place
Alias: None
Product: Red Hat Linux
Classification: Retired
Component: sysreport
Version: 8.0
Hardware: All
OS: Linux
Target Milestone: ---
Assignee: Ngo Than
QA Contact: Ben Levenson
Depends On:
TreeView+ depends on / blocked
Reported: 2002-11-08 19:31 UTC by Ulrich Drepper
Modified: 2007-04-18 16:48 UTC (History)
0 users

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Last Closed: 2002-11-08 19:31:30 UTC

Attachments (Terms of Use)

System ID Priority Status Summary Last Updated
Red Hat Product Errata RHBA-2004:094 normal SHIPPED_LIVE Updated sysreport package includes bugfixes, enhancements 2004-04-21 04:00:00 UTC

Description Ulrich Drepper 2002-11-08 19:31:24 UTC
From Bugzilla Helper:
User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.2b) Gecko/20021102

Description of problem:
Running sysreport on a RHL8 system shows:

Sendmail Configuration (/etc/                 [FAILED]

This is obviously wrong since the config is in /etc/mail/

Version-Release number of selected component (if applicable):

How reproducible:

Steps to Reproduce:
1.Run sysreport on a system with sendmail installed

Actual Results:  /etc/ search

Expected Results:  /etc/mail/ searched

Additional info:

Comment 1 Ngo Than 2002-11-12 11:15:37 UTC
it's fixed in 1.3.1 or newer. You will find it in next rawhide release.

Comment 2 John Flanagan 2004-04-22 01:09:12 UTC
An errata 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.