Jeffrey Young
Very Senior Member
I am using Merlin 388.8_4 on an AX86U-Pro. Using Diversion and Skynet (and a few of my own written scripts)
Over the last few months, I have noticed that the dnsmasq.conf.add file has the execute attribute set. After I take the execute bit off, a few days later, it is set again. I have not really nailed down what process is doing this.
Having the execute bit set on a file that does not need it is having the unintended effect of Asus's ASD process zapping the file from time to time. Particularly at system boot, which really messes things up.
Anyone else seeing this behavior? I would love to be able to lock the file so that attributes can't be set, but as almost everything runs as root, that is not happening.
Over the last few months, I have noticed that the dnsmasq.conf.add file has the execute attribute set. After I take the execute bit off, a few days later, it is set again. I have not really nailed down what process is doing this.
Having the execute bit set on a file that does not need it is having the unintended effect of Asus's ASD process zapping the file from time to time. Particularly at system boot, which really messes things up.
Anyone else seeing this behavior? I would love to be able to lock the file so that attributes can't be set, but as almost everything runs as root, that is not happening.