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:

After installed xinetd on RHEL7, stop| restart| xined the following error message will output , Does it an excepted message?

===
Jul 12 12:10:07 R74Router xinetd[21866]: unexpected signal: 18 (Continued) in signal pipe
Jul 12 12:10:07 R74Router systemd: Stopping Xinetd A Powerful Replacement For Inetd...
Jul 12 12:10:07 R74Router xinetd[21866]: Exiting...
===
Version-Release number of selected component (if applicable):

I have reproduced it on RHEL7.1~7.5

How reproducible:

Steps to Reproduce:
1. # yum install xinetd -y
2. # systemctl stop xinetd
3. # systemctl restart xinetd


Actual results:

error message output.

Expected results:

no error message output.

Additional info:

This is harmless. Xinetd merely informs that it got a SIGCONT from systemd. This behaviour is currently not documented, but I'm planning on fixing that soon (see https://bugzilla.redhat.com/show_bug.cgi?id=1601794). Since this is (will be...) a well documented case, I could patch xinetd to simply not log anything if it gets a SIGCONT.

Also, I strongly recommend to use native systemd units instead of xinetd. I can help with the translation if you want.

See https://bugzilla.redhat.com/show_bug.cgi?id=1601794.