Bug 947851

Summary:	the Bip systemd service file uses a PIDFile path that is not configured
Product:	[Fedora] Fedora	Reporter:	Josh <jokajak>
Component:	bip	Assignee:	Brian Lane <bcl>
Status:	CLOSED INSUFFICIENT_DATA	QA Contact:	Fedora Extras Quality Assurance <extras-qa>
Severity:	unspecified	Docs Contact:
Priority:	unspecified
Version:	18	CC:	bcl, dpierce, mmahut
Target Milestone:	---
Target Release:	---
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:		Doc Type:	Bug Fix
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2013-06-05 17:26:30 UTC	Type:	Bug
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Embargoed:

Description Josh 2013-04-03 12:27:17 UTC

Description of problem:
the PIDFile in the service definition points to /run/bip/bip.pid but this directory doesn't exist (and can't by default because it is a tmpfs).

Version-Release number of selected component (if applicable):
0.8.8-7.fc18.armv5tel

How reproducible:
always

Steps to Reproduce:
1. yum install bip
2. systemctl start bip.service
3.
  
Actual results:
bip fails to start

Expected results:
bip starts

Additional info:
changing the PIDFile=/run/bip/bip.pid to PIDFile=/var/run/bip/bip.pid in bip.service fixes it

Comment 1 Brian Lane 2013-04-26 18:20:53 UTC

Do you have a /etc/tmpfiles.d/bip.conf installed? This is supposed to setup the directory. Also, /var/run/ should be a symlink to /run/