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.
DescriptionChristoph Galuschka
2013-09-28 19:54:35 UTC
Description of problem:
rsync has an xinetd configuration file in /etc/xinetd.d/rsync (similar to telnet-server). Unlike telnet-server, rsync does NOT have xinetd as requirement in the spec-file.
Allthough a daemon mode is available in rsync, there is no rsync in /etc/init.d. So one would require xinetd.
Version-Release number of selected component (if applicable):
rsync-3.0.6-9
How reproducible:
always
Steps to Reproduce:
1. install rsync, xinetd does not get pulled in as dependency.
Actual results:
xinetd is not installed as dependency
Expected results:
xinetd gets installed as dependency
Additional info:
Comment 2RHEL Program Management
2013-10-13 23:05:43 UTC
This request was evaluated by Red Hat Product Management for
inclusion in the current release of Red Hat Enterprise Linux.
Because the affected component is not scheduled to be updated
in the current release, Red Hat is unable to address this
request at this time.
Red Hat invites you to ask your support representative to
propose this request, if appropriate, in the next release of
Red Hat Enterprise Linux.
Comment 3Christoph Galuschka
2013-10-16 19:10:53 UTC
in my humble opinion this does not require an update of rsync or xinetd. A simple change to the spec file should be enough to add that requirement. Except if that is also considered an update.
Comment 4Christoph Galuschka
2013-10-17 06:23:04 UTC
Pavel: The use case is running rsync as a server software from which to pull the changes. Yes, that is certainly something where anonymous access is used. I admit I don't know where to find the requirement to install xinetd for anonymous access, but I think it would be nice if that requirement is also reflected in the package by pulling in xinetd as dep.
Comment 5Pavel Šimerda (pavlix)
2013-10-17 07:10:56 UTC
1) I don't see one the requirement of one additional step ('yum install xinetd') as a satisfactory argument to add an unwanted dependency for the huge number of command-line rsync users. So far for my personal opinion.
2) Adding such a dependency in an update to el6 would cause 'xinetd' to be forcedly installed during a system update. I can only guess that this is a *no-go* whether or not your request is valid or not.
3) Any modification to a package results in a new release of the package being created, therefore it's considered an update and it's a process on its own.
We value community feedback but your report would be better suited for a recent version for the Fedora distribution where active development is being done.
Comment 6Pavel Šimerda (pavlix)
2013-10-17 07:54:19 UTC
(In reply to Pavel Šimerda from comment #5)
> 2) Adding such a dependency in an update to el6 would cause 'xinetd' to be
> forcedly installed during a system update. I can only guess that this is a
> *no-go* whether or not your request is valid or not.
Confirmed.