Bug 664791

Summary: impossible to tell radvd to not write any pidfile.
Product: Red Hat Enterprise Linux 6 Reporter: Laine Stump <laine>
Component: radvdAssignee: Jiri Skala <jskala>
Status: CLOSED NOTABUG QA Contact: qe-baseos-daemons
Severity: medium Docs Contact:
Priority: low    
Version: 6.0CC: aglotov
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: 2010-12-23 09:00: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:
Embargoed:

Description Laine Stump 2010-12-21 16:39:47 UTC 
If you don't specify a pidfile location, radvd will write one to /var/run/radvd.pid. If you happen to not want any pidfile (eg, because you're running radvd with "-d 1" so that it won't daemonize, and are planning to write your own pidfile), there is no way to specify this.

A naive attempt to use "--pidfile /dev/null" shows that radvd assumes that what it reads from the file you provide is a valid number (it calls atol() so there is no error checking, and ends up thinking that radvd is running as pid 0).

There should be some way to tell radvd to not create a pidfile (or perhaps when it doesn't daemonize, lack of a --pidfile option should mean "you won't be detaching, so don't create a pidfile).
Comment 2 Jiri Skala 2010-12-23 09:00:58 UTC 
Radvd checks if there is no another running instance. Therefore creation of pid file is not a bug.

I suppose your difficulties could fix option -s - single process.