Bug 751234

Summary: svnserve not in /etc/services
Product: Red Hat Enterprise Linux 6 Reporter: Matthew Saltzman <mjs>
Component: subversionAssignee: Joe Orton <jorton>
Status: CLOSED NOTABUG QA Contact: qe-baseos-daemons
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: 6.4   
Target Milestone: rc   
Target Release: ---   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2011-12-14 14:43:58 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:

Description Matthew Saltzman 2011-11-04 00:26:37 UTC 
Description of problem:
/etc/services does not contain an entry for svnserve/tcp.  When using xinetd to start svnserve on access, it reports 

"service/protocol combination not in /etc/services: svnserve/tcp"

and refuses to listen.

Version-Release number of selected component (if applicable):
subversion-1.6.11-2.el6_1.4.x86_64

How reproducible:
always

Steps to Reproduce:
1. Configure /etc/xinetd.d/svnserve
2. Restart xinetd
3. Try to connect to the svn port
  
Actual results:
Fail.

Expected results:
Connection to svnserve

Additional info:
Also true in RHEL5 and even in Fedora 15.  Do I need to file separate bugs?
Comment 2 RHEL Program Management 2011-11-04 00:48:49 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 unfortunately unable to
address this request at this time. Red Hat invites you to
ask your support representative to propose this request, if
appropriate and relevant, in the next release of Red Hat
Enterprise Linux. If you would like it considered as an
exception in the current release, please ask your support
representative.
Comment 3 Joe Orton 2011-12-14 14:43:58 UTC 
Thanks for the report.  The protocol name that was registered is "svn", so using that should work:

$ grep svn /etc/services 
svn             3690/tcp                        # Subversion
svn             3690/udp                        # Subversion