You can increase or make infinite the --socket-timeout ... but I'd say the default 600s ought to be plenty. Actually the --retries ... (there's --fragment-retries ... too) is only used in fetching the media data, although an extractor could implement its own retry mechanism using the same...
There is a default retry count of 10 for things that the code expects to be resolved by retrying. A timeout on connecting is, IIRC, not one of those.
Maybe we need to stop sending ancient UA strings in case iPlayer is blocking certain old UA strings. A random UA from a list made up when...
But possibly the same config options that work for 1.20 might get a long way to building the current version. I think it was 1.29 when I last tried but 1.36.1 is the latest stable.
Ah yes, it can happen: who knows why?
It's possible that the help text in the CF BusyBox doesn't match the actual s/w. These strings that appear to include data for option parsing are together in the output of strings /bin/busybox :
udhcp 1.20.2
O::x::T+:t+:A+:vv...
In the wifi-up script that I massaged, I had this code after supposedly setting the wifi and network params:
...
# if manual config then
# apply config
else
# wait for PHY connection
while ! isConnected "$wif"; do
sleep 2
done
eth_check
echo "$(date -Iseconds -u) DHCP:"
# file holds...
I think the Humax settop code will try to reset to its built-in default if it thinks the network settings aren't working. Maybe this is just checked at a certain point rather than continually. The assumption has always been that this is a get-out-of-jail feature used by the original devs.
It seems that more of wireless-helper may need to be rolled into the CFW itself, bearing in mind https://hummy.tv/forum/threads/wifi-unreliable-when-booting-into-maintenance-mode.10601/post-161961. Or maybe I'm behind the curve.
On reflection general or advanced would be better than web. One might consider why the modules in the settings don't directly correspond to subdirectories of /mod/webif/html: what sort of modules are they?
+1
Really, the answer is just to make a manual backup when you're happy with the setup and want something that can be restored.
However, if one wanted to make the expiration configurable, it's a question of directed plagiarism:
the backup code is in /mod/webif/html/sched/backup
the settings code...
Resolving the shellcheck diagnostics probably won't fix anything except a nagging feeling that there is shell code with known problematic constructs. Some of the diagnostics seem fair and the actual suggestions seem mostly OK. The SC2010 issues (ls -1 | grep ..., no suggestion) would need a bit...
If any username/pwd is set for Webif (uses /mod/etc/htpasswd, settable from GUI Settings>Web Interface Settings), you would have to supply whatever authentication the lighttpd server expects. As I've never set up authentication, I can't say how that should happen, except that you can check what...
Whereas the Backup/Restore schedule is every night.
Obviously there is a need for historical backups as well as a last known good. I am sceptical about using a frequent backup here because I have seen empty scheduled backups being saved overnight when the next restart shows an "uncommanded...
After an uncommanded reset, the autoschedule restore operation did not seem to be run although a valid autoschedule backup file was present. Where is the 1.4 script called with restore?
I think it used to work like this:
the script is run as a cron job after the system restarts
if the schedule...
Indeed, that's how the WebIf works.
The web server routes each incoming request to a Jim script (adding index.jim if the URL mentions no specific script in a directory specified by the URL. The procedure writes out any suitable response as a web page, or other data, to be sent back to the...
man lsof reveals various parameters that might be relevant:
...
-b causes lsof to avoid kernel functions that might block -
lstat(2), readlink(2), and stat(2).
...
-f ...
...
When -f is specified by itself, all path name...
You can increase or make infinite the --socket-timeout ... but I'd say the default 600s ought to be plenty. Actually the --retries ... (there's --fragment-retries ... too) is only used in fetching the media data, although an extractor could implement its own retry mechanism using the same...
There is a default retry count of 10 for things that the code expects to be resolved by retrying. A timeout on connecting is, IIRC, not one of those.
Maybe we need to stop sending ancient UA strings in case iPlayer is blocking certain old UA strings. A random UA from a list made up when...
But possibly the same config options that work for 1.20 might get a long way to building the current version. I think it was 1.29 when I last tried but 1.36.1 is the latest stable.
Ah yes, it can happen: who knows why?
It's possible that the help text in the CF BusyBox doesn't match the actual s/w. These strings that appear to include data for option parsing are together in the output of strings /bin/busybox :
udhcp 1.20.2
O::x::T+:t+:A+:vv...
In the wifi-up script that I massaged, I had this code after supposedly setting the wifi and network params:
...
# if manual config then
# apply config
else
# wait for PHY connection
while ! isConnected "$wif"; do
sleep 2
done
eth_check
echo "$(date -Iseconds -u) DHCP:"
# file holds...
I think the Humax settop code will try to reset to its built-in default if it thinks the network settings aren't working. Maybe this is just checked at a certain point rather than continually. The assumption has always been that this is a get-out-of-jail feature used by the original devs.
It seems that more of wireless-helper may need to be rolled into the CFW itself, bearing in mind https://hummy.tv/forum/threads/wifi-unreliable-when-booting-into-maintenance-mode.10601/post-161961. Or maybe I'm behind the curve.
On reflection general or advanced would be better than web. One might consider why the modules in the settings don't directly correspond to subdirectories of /mod/webif/html: what sort of modules are they?
+1
Really, the answer is just to make a manual backup when you're happy with the setup and want something that can be restored.
However, if one wanted to make the expiration configurable, it's a question of directed plagiarism:
the backup code is in /mod/webif/html/sched/backup
the settings code...
Resolving the shellcheck diagnostics probably won't fix anything except a nagging feeling that there is shell code with known problematic constructs. Some of the diagnostics seem fair and the actual suggestions seem mostly OK. The SC2010 issues (ls -1 | grep ..., no suggestion) would need a bit...
If any username/pwd is set for Webif (uses /mod/etc/htpasswd, settable from GUI Settings>Web Interface Settings), you would have to supply whatever authentication the lighttpd server expects. As I've never set up authentication, I can't say how that should happen, except that you can check what...
Whereas the Backup/Restore schedule is every night.
Obviously there is a need for historical backups as well as a last known good. I am sceptical about using a frequent backup here because I have seen empty scheduled backups being saved overnight when the next restart shows an "uncommanded...
After an uncommanded reset, the autoschedule restore operation did not seem to be run although a valid autoschedule backup file was present. Where is the 1.4 script called with restore?
I think it used to work like this:
the script is run as a cron job after the system restarts
if the schedule...
Indeed, that's how the WebIf works.
The web server routes each incoming request to a Jim script (adding index.jim if the URL mentions no specific script in a directory specified by the URL. The procedure writes out any suitable response as a web page, or other data, to be sent back to the...
man lsof reveals various parameters that might be relevant:
...
-b causes lsof to avoid kernel functions that might block -
lstat(2), readlink(2), and stat(2).
...
-f ...
...
When -f is specified by itself, all path name...
This site uses cookies to help personalise content, tailor your experience and to keep you logged in if you register.
By continuing to use this site, you are consenting to our use of cookies.