[Bug 1835446] Re: radvd unit still references /var/run for pidfile

2019-09-06 Thread Launchpad Bug Tracker
[Expired for radvd (Ubuntu) because there has been no activity for 60 days.] ** Changed in: radvd (Ubuntu) Status: Incomplete => Expired -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1835446

[Bug 1835446] Re: radvd unit still references /var/run for pidfile

2019-07-08 Thread Rafael David Tinoco
Hello Michael, One thing I have noticed about this: (c)inaddy@temp:~$ systemctl status radvd ● radvd.service - Router advertisement daemon for IPv6 Loaded: loaded (/lib/systemd/system/radvd.service; disabled; vendor preset: enabled) Active: inactive (dead) Docs: man:radvd(8) Jul 08

[Bug 1835446] Re: radvd unit still references /var/run for pidfile

2019-07-08 Thread Rafael David Tinoco
Could you please provide me the EXACT steps you're executing so we can reproduce exactly what is going on in your system ? The only thing I could find is this "missing config file" by default and "enabling service by default" <- which we could address in this bug, unless you have something else.

[Bug 1835446] Re: radvd unit still references /var/run for pidfile

2019-07-07 Thread Michael Griego
The compat mapping is present. I should have clarified that the behavior didn't manifest itself until a system restart. The first time I started up the service with a valid config, it ran. After I rebooted the system, the service no longer came up and presented with the error message I included

[Bug 1835446] Re: radvd unit still references /var/run for pidfile

2019-07-05 Thread Christian Ehrhardt 
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.

[Bug 1835446] Re: radvd unit still references /var/run for pidfile

2019-07-05 Thread Christian Ehrhardt 
Thank you for your report Michael, The issue this report is about is present in Debian too. Ubuntu doesn't normally make any changes over the Debian in development releases but syncs them, so this bug would be best fixed directly in Debian, and then Ubuntu will pick up the fix automatically.