Bug 754074

Summary:	Add SystemD startup script for svnserve
Product:	[Fedora] Fedora	Reporter:	Roy <nouveau>
Component:	subversion	Assignee:	Joe Orton <jorton>
Status:	CLOSED ERRATA	QA Contact:	Fedora Extras Quality Assurance <extras-qa>
Severity:	medium	Docs Contact:
Priority:	unspecified
Version:	16	CC:	jorton, vanmeeuwen+fedora, ville.skytta
Target Milestone:	---
Target Release:	---
Hardware:	All
OS:	Linux
Whiteboard:
Fixed In Version:	subversion-1.7.4-1.fc17	Doc Type:	Bug Fix
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2012-03-21 18:41:47 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 Roy 2011-11-15 11:06:34 UTC

Description of problem:
Svnserve currently relies on a SysV script to start up. With Fedoras move towards SystemD it would be beneficial to add a simple start-up script for SystemD instead.

Version-Release number of selected component (if applicable):
1.6.17-5.FC16

Additional info:
My personal setup is using a separate "svn" user to start the daemon. The following two files will make sure svnserve can start as a daemon with user svn. The first will create a temporary directory in /var/run to store the PIDFile in (with write access for the svn user), the second defines the service. As default root I chose /var/svn (must of course exist with r/w access for the svn user), parallel to /var/www used by default for httpd webpages.

/etc/tmpfiles.d/svnd.conf:
d /var/run/svnd 0755 svn svn -

/lib/systemd/system/svnd.service:
[Unit]
Description=SVN Server
After=network.target

[Service]
Type=forking
PIDFile=/var/run/svnd/svnd.pid
User=svn
ExecStart=/usr/bin/svnserve -d -r /var/svn --pid-file /var/run/svnd/svnd.pid

[Install]
WantedBy=multi-user.target

Comment 1 Fedora Update System 2012-02-29 13:25:46 UTC

subversion-1.7.3-4.fc17 has been submitted as an update for Fedora 17.
https://admin.fedoraproject.org/updates/subversion-1.7.3-4.fc17

Comment 2 Fedora Update System 2012-02-29 18:52:27 UTC

Package subversion-1.7.3-4.fc17:
* should fix your issue,
* was pushed to the Fedora 17 testing repository,
* should be available at your local mirror within two days.
Update it with:
# su -c 'yum update --enablerepo=updates-testing subversion-1.7.3-4.fc17'
as soon as you are able to.
Please go to the following url:
https://admin.fedoraproject.org/updates/FEDORA-2012-2673/subversion-1.7.3-4.fc17
then log in and leave karma (feedback).

Comment 3 Fedora Update System 2012-03-02 01:01:09 UTC

Package subversion-1.7.3-7.fc17:
* should fix your issue,
* was pushed to the Fedora 17 testing repository,
* should be available at your local mirror within two days.
Update it with:
# su -c 'yum update --enablerepo=updates-testing subversion-1.7.3-7.fc17'
as soon as you are able to.
Please go to the following url:
https://admin.fedoraproject.org/updates/FEDORA-2012-2673/subversion-1.7.3-7.fc17
then log in and leave karma (feedback).

Comment 4 Fedora Update System 2012-03-12 19:09:31 UTC

Package subversion-1.7.4-1.fc17:
* should fix your issue,
* was pushed to the Fedora 17 testing repository,
* should be available at your local mirror within two days.
Update it with:
# su -c 'yum update --enablerepo=updates-testing subversion-1.7.4-1.fc17'
as soon as you are able to.
Please go to the following url:
https://admin.fedoraproject.org/updates/FEDORA-2012-2673/subversion-1.7.4-1.fc17
then log in and leave karma (feedback).

Comment 5 Fedora Update System 2012-03-21 18:41:47 UTC

subversion-1.7.4-1.fc17 has been pushed to the Fedora 17 stable repository.  If problems still persist, please make note of it in this bug report.