Bug 670793

Summary:	startproc -p fails to use specified pidfile
Product:	[openSUSE] openSUSE 11.3	Reporter:	Fredrick Woolard <woolardfa>
Component:	Basesystem	Assignee:	E-mail List <bnc-team-screening>
Status:	VERIFIED INVALID	QA Contact:	E-mail List <qa-bugs>
Severity:	Normal
Priority:	P5 - None
Version:	Final
Target Milestone:	---
Hardware:	All
OS:	openSUSE 11.3
Whiteboard:
Found By:	---	Services Priority:
Business Priority:		Blocker:	---
Marketing QA Status:	---	IT Deployment:	---

Description Fredrick Woolard 2011-02-09 22:13:47 UTC

User-Agent:       Mozilla/5.0 (X11; U; Linux x86_64; en-US; rv:1.9.2.13) Gecko/20101203 SUSE/3.6.13-0.2.1 Firefox/3.6.13

Using startproc -p to specify a particular pidfile when starting a daemon fails to use that specified pidfile, and reverts to using the default /var/run/<basename>.pid file name.

 

Reproducible: Always

Steps to Reproduce:
1. Copy the /etc/apache2 dir to /etc/apache2-alt0
2. Adjust either the listen.conf, default-server.conf or appropriate vhosts.d entry so there is no collision for binding to ip/port, i.e. set up the alt0 to listent on 8080.
3.Issue command: startproc -p /var/run/httpd2alt0.pid -t2 /usr/sbin/httpd2-prefork -f /etc/apache2-alt0/httpd.conf -DSSL
Actual Results:  
The /var/run/httpd2.pid file is present

Expected Results:  
Should see /var/run/httpd2-alt0.pid file

Comment 1 Fredrick Woolard 2011-02-09 22:35:06 UTC

Failed to adjust PidFile option in alternate configs. Reporter unaware of entity responsible for establishing the pid file, which is httpd2.