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
When setting up services in the luci-interface, pressing the "Speichern und Anwenden" Button looks like not applying the configuration properly. It does store the values right, but nothing happens else
This line sets a watchdog on the ffservices-file in /etc/config/ffservices, where the service-data is stored. When changes in that file are registered by LuCI-Webinterface, it will trigger the one-shot service ffserviced to write the new information into OLSR and uhttpd.
Apparently the quotes around ffservices prevent this workflow sometimes.
Solving the issue
To solve this issue, one needs to verify, that the quotes are the cause of the issue, as there is also user experience, that it was working in that way. For me, It worked once I edited the file in that way. But maybe it was just caused by editing the file, whatever.
The text was updated successfully, but these errors were encountered:
Behaviour
When setting up services in the luci-interface, pressing the "Speichern und Anwenden" Button looks like not applying the configuration properly. It does store the values right, but nothing happens else
Possible cause
In
/etc/init.d/ffserviced
there's a lineThis line sets a watchdog on the ffservices-file in
/etc/config/ffservices
, where the service-data is stored. When changes in that file are registered by LuCI-Webinterface, it will trigger the one-shot serviceffserviced
to write the new information into OLSR and uhttpd.Apparently the quotes around
ffservices
prevent this workflow sometimes.Solving the issue
To solve this issue, one needs to verify, that the quotes are the cause of the issue, as there is also user experience, that it was working in that way. For me, It worked once I edited the file in that way. But maybe it was just caused by editing the file, whatever.
The text was updated successfully, but these errors were encountered: