3:38 a.m.
Hi,
If I run it as is, I get:
Dec 27 13:27:21 yuri iwd[716]: cp: cannot create regular file
'/etc/resolv.conf.bak': Read-only file system
Dec 27 13:27:21 yuri iwd[717]: /usr/lib/resolvconf/libc: line 230:
/etc/resolv.conf: Read-only file system
Dec 27 13:27:21 yuri iwd[761]: cp: cannot create regular file
'/etc/resolv.conf.bak': Read-only file system
Dec 27 13:27:21 yuri iwd[762]: /usr/lib/resolvconf/libc: line 230:
/etc/resolv.conf: Read-only file system
I can work around it by:
touch /etc/resolv.conf.bak
and overriding:
[Service]
ReadWritePaths=/etc/resolv.conf.bak
ReadWritePaths=/etc/resolv.conf
Others suggested another way to fix it:
RuntimeDirectory=resolvconf
ReadWritePaths=/etc/resolv.conf
https://bugs.archlinux.org/task/67069
Can src/iwd.service.in be adjusted?
Regards,
Yuri
11:05 a.m.
Hi Yuri,
<snip>
[Service]
ReadWritePaths=/etc/resolv.conf.bak
ReadWritePaths=/etc/resolv.conf
Others suggested another way to fix it:
RuntimeDirectory=resolvconf
ReadWritePaths=/etc/resolv.conf
https://bugs.archlinux.org/task/67069
Can src/iwd.service.in be adjusted?
I think this or a similar issue has come up before. The problem is that iwd
supports either systemd-resolved or resolvconf. So for systems that use
systemd-resolved (which iwd defaults to), punching this security policy
exception is not needed and arguably it should not be enabled by default.
Perhaps as a compromise we may be able to ship service.in with these lines added
& commented out. Not sure if this would be of any help though. Other ideas are
welcome.
Regards,
-Denis
142
days inactive
149
days old
1 comments
2 participants
participants (2)
-
Denis Kenzior -
Yuri Kanivetsky