You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Bind-mounting /tmp/resolv.conf.auto apparently doesn't forward inotify events arriving from the kernel when resolv.conf.auto was changed (e.g. upstream DNS servers were received by a DHCP client or pppd). Restarting dnsmasq or running it without ujail solves the issue.
The text was updated successfully, but these errors were encountered:
Hi Daniel,
It's one of the limitations of bind mounts, what you see in the jail is the file with inode 3400 and never the one with inode 3897, because what you really changed is /tmp
There is 2 workarounds:
write to the file instead of replacing it with a new one (with mv/rename). With this option you loose the atomicity of the rename
bind mount the parent dir of the file, bind mouting /tmp is not a good idea but maybe you can move resolv.conf.auto in a dnsmasq dir
May I propose that netifd write not to /tmp/resolv.conf.auto but to /tmp/netifd/resolv.conf or similar, so that /tmp/netifd can be mounted into the jail as a directory and inotify will work?
dangowrt:
Bind-mounting /tmp/resolv.conf.auto apparently doesn't forward inotify events arriving from the kernel when resolv.conf.auto was changed (e.g. upstream DNS servers were received by a DHCP client or pppd). Restarting dnsmasq or running it without ujail solves the issue.
The text was updated successfully, but these errors were encountered: