Note: This bug is displayed in read-only format because
the product is no longer active in Red Hat Bugzilla.
RHEL Engineering is moving the tracking of its product development work on RHEL 6 through RHEL 9 to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "RHEL project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs in the statuses "NEW", "ASSIGNED", and "POST" are being migrated throughout September 2023. Bugs of Red Hat partners with an assigned Engineering Partner Manager (EPM) are migrated in late September as per pre-agreed dates. Bugs against components "kernel", "kernel-rt", and "kpatch" are only migrated if still in "NEW" or "ASSIGNED". If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "RHEL project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/RHEL-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.
Description of problem:
when xinetd is running then chkconfig should start xinetd_services
Version-Release number of selected component (if applicable):
Red Hat Enterprise Linux Server release 7.0 Alpha1 (Maipo)
How reproducible:
deterministic
Steps to Reproduce:
1. # service xinetd restart
Redirecting to /bin/systemctl restart xinetd.service
# service xinetd status
Redirecting to /bin/systemctl status xinetd.service
xinetd.service - Xinetd A Powerful Replacement For Inetd
Loaded: loaded (/lib/systemd/system/xinetd.service; enabled)
Active: active (running) since Tue, 06 Mar 2012 09:56:22 -0500; 2min 27s ago
Process: 13987 ExecStart=/usr/sbin/xinetd -stayalive -pidfile /var/run/xinetd.pid $EXTRAOPTIONS (code=exited, status=0/SUCCESS)
Main PID: 13991 (xinetd)
CGroup: name=systemd:/system/xinetd.service
└ 13991 /usr/sbin/xinetd -stayalive -pidfile /var/run/xinetd.pid
2. # rdate -p localhost
rdate: couldn't connect to host localhost: Connection refused
3. # chkconfig time-dgram on
4. # chkconfig time-stream on
5. # rdate -p localhost
rdate: couldn't connect to host localhost: Connection refused
6. # service xinetd restart
Redirecting to /bin/systemctl restart xinetd.service
7. # rdate -p localhost
rdate: [localhost] Tue Mar 6 09:52:08 2012
Actual results:
xinetd restart is needed. Its different behavior compare to rhel[56]
Expected results:
no xinetd restart is needed
step 5 should work
Additional info:
this is rhel6 behavior:
[root@hp-xw4200-01 tmp.NtQszGdpJ5]# rdate -p localhost
rdate: couldn't connect to host localhost: Connection refused
[root@hp-xw4200-01 tmp.NtQszGdpJ5]# chkconfig time-stream on
[root@hp-xw4200-01 tmp.NtQszGdpJ5]# chkconfig time-dgram on
[root@hp-xw4200-01 tmp.NtQszGdpJ5]# rdate -p localhost
rdate: [localhost] Tue Mar 6 09:58:10 2012