RHEL Engineering is moving the tracking of its product development work on RHEL 6 through RHEL 9 to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "RHEL project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs in the statuses "NEW", "ASSIGNED", and "POST" are being migrated throughout September 2023. Bugs of Red Hat partners with an assigned Engineering Partner Manager (EPM) are migrated in late September as per pre-agreed dates. Bugs against components "kernel", "kernel-rt", and "kpatch" are only migrated if still in "NEW" or "ASSIGNED". If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "RHEL project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/RHEL-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.

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).

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.