Bug 85371 - xinetd regression - doesn't accept valid facility on log_type SYSLOG (e.g. mail)
xinetd regression - doesn't accept valid facility on log_type SYSLOG (e.g. m...
Product: Red Hat Linux
Classification: Retired
Component: xinetd (Show other bugs)
i386 Linux
medium Severity medium
: ---
: ---
Assigned To: Jay Fenlason
Brock Organ
Depends On:
  Show dependency treegraph
Reported: 2003-02-28 13:25 EST by John Gerth
Modified: 2014-08-31 19:24 EDT (History)
1 user (show)

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Last Closed: 2003-05-13 13:14:05 EDT
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

Attachments (Terms of Use)
testcase showing failure with xinetd for imap (1.77 KB, text/plain)
2003-02-28 13:28 EST, John Gerth
no flags Details

External Trackers
Tracker ID Priority Status Summary Last Updated
Red Hat Product Errata RHSA-2003:160 normal SHIPPED_LIVE : Updated xinetd packages fix a denial-of-service attack and other bugs 2003-05-13 00:00:00 EDT
Red Hat Product Errata RHSA-2003:161 normal SHIPPED_LIVE Important: xinetd security update 2003-05-22 00:00:00 EDT

  None (edit)
Description John Gerth 2003-02-28 13:25:49 EST
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):

How reproducible:

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 -

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)
Comment 1 John Gerth 2003-02-28 13:28:54 EST
Created attachment 90428 [details]
testcase showing failure with xinetd for imap
Comment 2 Mark J. Cox 2003-05-13 13:14:06 EDT
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.