Bug 91350 - Upgrade to xinetd-2.3.11-1.8.0 cause not function on qmail-pop3 server
Upgrade to xinetd-2.3.11-1.8.0 cause not function on qmail-pop3 server
Status: CLOSED NOTABUG
Product: Red Hat Linux
Classification: Retired
Component: xinetd (Show other bugs)
8.0
i686 Linux
medium Severity medium
: ---
: ---
Assigned To: Jay Fenlason
Brock Organ
:
Depends On:
Blocks:
  Show dependency treegraph
 
Reported: 2003-05-21 16:08 EDT by Cattaneo Fabrizio
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:
Environment:
Last Closed: 2003-05-21 16:15:31 EDT
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---


Attachments (Terms of Use)

  None (edit)
Description Cattaneo Fabrizio 2003-05-21 16:08:24 EDT
From Bugzilla Helper:
User-Agent: Mozilla/4.0 (compatible; MSIE 6.0; Windows NT 5.0; Virgilio6pc)

Description of problem:
Sorry for my bad english.... ;-))

Yesterday i have upgrade my xinetd  ( on linux R.H. 8.0 server ) with the new 
version supply .... ref . RHSA-2003:160

after the change the qmail-pop3 server dont work....

I attack the file used for configure xinetd to start qmail-pop3 server.

Thanks in advance ,
Cattaneo Fabrizio.

service pop3
{
disable = no
socket_type = stream
protocol = tcp
wait = no
user = root
server = /var/qmail/bin/qmail-popup
server_args = host.dominio.it/home/vpopmail/bin/vchkpw
/var/qmail/bin/qmail-pop3d Maildir
log_type = FILE /var/log/xinetd.log
log_on_success = HOST
log_on_failure = HOST RECORD
}


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

How reproducible:
Always

Steps to Reproduce:
1.Upgrade to xinetd-2.3.11-1.8.0
2.Restart xinetd
3.Services qmail-popup stop to work
    

Additional info:
Comment 1 Jay Fenlason 2003-05-21 16:15:31 EDT
Remove RECORD from the log_on_failure line.  In old versions of xinetd, this bad
(it never did anything) option was ignored.  In 2.3.11 it causes an error.

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