Bug 63042 - triggering xinetd hard reconfiguration with chkconfig
Summary: triggering xinetd hard reconfiguration with chkconfig
Alias: None
Product: Red Hat Public Beta
Classification: Retired
Component: xinetd (Show other bugs)
(Show other bugs)
Version: skipjack-beta2
Hardware: i386 Linux
Target Milestone: ---
Assignee: Trond Eivind Glomsrxd
QA Contact: Brock Organ
Depends On:
Blocks: 61590
TreeView+ depends on / blocked
Reported: 2002-04-09 15:48 UTC by Michael Schwendt
Modified: 2007-04-18 16:41 UTC (History)
1 user (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Last Closed: 2002-04-10 23:15:55 UTC
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

Attachments (Terms of Use)

Description Michael Schwendt 2002-04-09 15:48:48 UTC
From Bugzilla Helper:
User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:0.9.9) Gecko/20020401

Description of problem:
With Enigma and earlier, one could toggle xinetd maintained services with just
chkconfig. "chkconfig wu-ftpd on" would not just create the proper links for the
current run-level, but would also send a USR2 signal to xinetd, causing a hard
reconfiguration and wu-ftpd being enabled. The exact opposite would happen for
"chkconfig wu-ftpd off". It would create the run-level link and signal xinetd to
re-read its config, stopping listening on the wu-ftpd port.

Besides the change from SIGUSR2 to SIGHUP, I see a major (still undocumented)
difference on Skipjack beta2.  "chkconfig wu-ftpd on" does NOT signal xinetd to
re-read its config. But "chkconfig wu-ftpd off" still does. Unless this is a
bug, it should be documented somewhere (the documentation for Enigma was wrong),
that "chkconfig wu-ftpd on" is not the opposite of "chkconfig wu-ftpd off" and
probably other xinetd maintained services:

# service xinetd status   
xinetd (pid 2337) is running...
# chkconfig --list wu-ftpd
wu-ftpd         off
# chkconfig wu-ftpd on
[log: xinetd: xinetd -HUP succeeded]
# chkconfig --list wu-ftpd
wu-ftpd         on
# socklist | grep xinetd

At this point -- unlike Enigma or earlier -- xinetd would not listen on ftp port

# service xinetd restart
[log: xinetd: xinetd shutdown succeeded
xinetd[2462]: xinetd Version 2002.03.26 started with libwrap options compiled in.
xinetd[2462]: Started working: 1 available service
xinetd: xinetd startup succeeded]
# socklist | grep xinetd
tcp     21      13110       0   2462    5  xinetd

This disables and stops it:

# chkconfig wu-ftpd off
[log: xinetd[2462]: Starting reconfiguration
xinetd[2462]: service ftp deactivated
xinetd[2462]: Reconfigured: new=0 old=0 dropped=1 (services)
xinetd: xinetd -HUP succeeded]
# socklist | grep xinetd

This enables it, but doesn't turn it on:

# chkconfig wu-ftpd on 
[log: xinetd: xinetd -HUP succeeded]
# socklist | grep xinetd

Version-Release number of selected component (if applicable):
xinetd 2.3.4-0.6 (plus chkconfig 1.3.4-1)

How reproducible:

Comment 1 Trond Eivind Glomsrxd 2002-04-09 16:43:45 UTC
It didn't send signals, but it does exec '/etc/inet.d/xinetd reload'.

Comment 2 Trond Eivind Glomsrxd 2002-04-09 16:48:31 UTC
Signal seems to be sent... taking back the bug :)

Comment 3 Trond Eivind Glomsrxd 2002-04-10 21:08:14 UTC
Confirmed as working on two systems, with xinetd-2.3.4-0.7 and xinetd-2.3.4-0.8.
No changes in that part.

Comment 4 Michael Schwendt 2002-04-10 21:40:28 UTC

# rpm -q xinetd

Comment 5 Michael Schwendt 2002-04-10 23:16:34 UTC
It's patch1 that fixes this bug.

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