Bug 85371
| Summary: | xinetd regression - doesn't accept valid facility on log_type SYSLOG (e.g. mail) | ||||||
|---|---|---|---|---|---|---|---|
| Product: | [Retired] Red Hat Linux | Reporter: | John Gerth <gerth> | ||||
| Component: | xinetd | Assignee: | Jay Fenlason <fenlason> | ||||
| Status: | CLOSED ERRATA | QA Contact: | Brock Organ <borgan> | ||||
| Severity: | medium | Docs Contact: | |||||
| Priority: | medium | ||||||
| Version: | 8.0 | CC: | jfeeney | ||||
| 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: | 2003-05-13 17:14:05 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: | |||||||
| Attachments: |
|
||||||
Created attachment 90428 [details]
testcase showing failure with xinetd for imap
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. http://rhn.redhat.com/errata/RHSA-2003-160.html |
Description of problem: While migrating mail service from 7.2 (xinetd-2.3.3-1) to 8.0 (xinetd-2.3.7-5), imap service fails to start because xinetd no longer recognizes "mail" as a valid SYSLOG facility. However "logger -p mail.info ..." works fine showing that the "mail" is a valid facility (see sample session below). I checked a few other facilities and some worked, some didn't. It's necessary for xinetd to allow all valid facilties to be specified so that we can keep the logs appropriately. Version-Release number of selected component (if applicable): xinetd-2.3.7-5 How reproducible: Always Steps to Reproduce: 1. set "log_type = SYSLOG mail" in some enabled service 2. restart xinetd 3. look at the complaint in /var/log/messages Actual results: Starting reconfiguration Feb 28 09:46:50 bissell xinetd[3101]: Unknown syslog facility: mail [line=11] Feb 28 09:46:50 bissell xinetd: xinetd -HUP succeeded Feb 28 09:46:50 bissell xinetd[3101]: Error parsing attribute log_type - DISABLING SERVICE [line=11] Expected results: xinetd should accept "mail" as a valid syslog facility Additional info: (This also happens with xinetd-2.3.7-4.7x on 7.3)