Doing some checks before reporting...

1:2.16-3 and 1:2.17-2 still list the path with /var (man page):
   -p pidfile, --pidfile pidfile
      Specifies an alternate pidfile. Normally the compiled in default 
/var/run/radvd.pid is used.

The path isn't overwritten in the systemd service either.

Using the most trivial radvd.conf imaginable
# cat /etc/radvd.conf 
interface foo {
  IgnoreIfMissing on;
};

The service works fine.
root@e:~# systemctl status radvd
● radvd.service - Router advertisement daemon for IPv6
   Loaded: loaded (/lib/systemd/system/radvd.service; disabled; vendor preset: 
enabled)
   Active: active (running) since Fri 2019-07-05 07:54:59 UTC; 2s ago
     Docs: man:radvd(8)
  Process: 12726 ExecStartPre=/usr/sbin/radvd --logmethod stderr_clean 
--configtest (code=exited, status=0/SUCCESS)
  Process: 12727 ExecStart=/usr/sbin/radvd --logmethod stderr_clean 
(code=exited, status=0/SUCCESS)
 Main PID: 12728 (radvd)
    Tasks: 2 (limit: 4915)
   Memory: 1000.0K
   CGroup: /system.slice/radvd.service
           ├─12728 /usr/sbin/radvd --logmethod stderr_clean
           └─12729 /usr/sbin/radvd --logmethod stderr_clean

And through the compat mapping for /var/run the pid still works:
ll /var/run /var/run/radvd.pid
lrwxrwxrwx 1 root root 4 Jun 23 07:52 /var/run -> /run/
-rw-r--r-- 1 root root 6 Jul  5 07:54 /var/run/radvd.pid
$ cat /var/run/radvd.pid
12728


Is in your case the compat mapping via the symlink missing/broken?

P.S. I'm still pinging people to take a look after radvd in general ...

** Changed in: radvd (Ubuntu)
       Status: Confirmed => Incomplete

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1835446

Title:
  radvd unit still references /var/run for pidfile

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/radvd/+bug/1835446/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

Reply via email to