[Bug 1907878] Re: wrong var declaration in if-up.d/resolved (nm-dispatcher[54417]: /etc/network/if-up.d/resolved: 12: mystatedir: not found)
Wladimir J. van der Laan
1907878 at bugs.launchpad.net
Fri Mar 25 13:51:56 UTC 2022
FWIW this is still a problem as of Ubuntu 22.04. I'm aware that using
/etc/network is deprecated in favor of netplan, I guess that's why the
script can stay in a broken state for so long. I'll be looking at
porting my configuration to that.
--
You received this bug notification because you are a member of Ubuntu
Foundations Bugs, which is subscribed to ifupdown in Ubuntu.
https://bugs.launchpad.net/bugs/1907878
Title:
wrong var declaration in if-up.d/resolved (nm-dispatcher[54417]:
/etc/network/if-up.d/resolved: 12: mystatedir: not found)
Status in ifupdown package in Ubuntu:
Confirmed
Bug description:
Syslog error:
nm-dispatcher[...]: /etc/network/if-up.d/resolved: 12: mystatedir:
not found
I think it's because of this line:
if systemctl is-enabled systemd-resolved > /dev/null 2>&1; then
mystatedir statedir ifindex interface <------------- this is interpreted as a 'mystatedir' command and fails
interface=$IFACE
if [ ! "$interface" ]; then
Perhaps the intention was to 'export mystatedir statedir ...'
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/ifupdown/+bug/1907878/+subscriptions
More information about the foundations-bugs
mailing list