Has anyone got any information or thoughts in this one.
I have been trying to get luci-access-control to work on the latest release and I have had to make an ugly one hack to get it too work properly.
/usr/sbin/inetacd.lua is called by
function mr.on_after_commit (self)
os.execute("/init.d/inetac restart >/dev/null 2>dev/null")
end
Where mr is a luci Map object.
Unfortunately on the wrt1900acs v2 router I am testing this it appears that /usr/sbin/inetacd.lua executes before the config file changes have actually finished being written to disk.
I suspect this is a multi-processor/multi-threading concurrency problem.
My ugly hack is to put a 5 second sleep at the start of inetacd.lua. This works.
So is Luci thread safe? Is there a better way to fix this?
Thoughts anyone.
Roger