what webif version does that? mine the latest does not do anything when clicking on pie chart.
Clicking on the pie-chart to display the Disk Utility option was introduced around July 2013 (or before), although the pie-chart function has has changed more recentlyMihaid : what webif version does that? mine the latest does not do anything when clicking on pie chart.
yes that's what the problem was, I knew clicking on the pie chart but it just was not working. Thanks for the update, it's all fine now.And the click was broken for some of the 1.0.17 train unless you clicked at a very specific place. That should be better with 1.0.18.
So turn off the disable with the plugin_autodisable/off diagnostic.So it's a bit alarming when I do so and find an "It crashed" message, because it could have happened some time ago and I'll find that something has been disabled for several days or more.
On the occasions it's happened I haven't had any e-mail. It's possible this has only happened on the non-RS box (only one of the two has RS enabled), but I'm fairly sure both have had 'unseen' crashes in the last few months.I thought RS provides an email alert if the linked HDR-FOX hasn't been seen for a period?
I thought the disable was to prevent the box getting stuck in a crash/reboot loop should it have been tripped up by a CFW feature. It is paramount that the box does its 'normal' functions of recording and playback as I'm not always around to sort problems out (and if there is going to be a problem 9/10 times it's when SWMBO is home alone - she has this effect on technology).So turn off the disable with the plugin_autodisable/off diagnostic.
I must have missed that one coming in. It would still be nice to be alerted when a disable has been effected even if a single crash is not alarmed.I thought the disable had been changed to a counter, rather than a single shot, so you shouldn't get things being disabled for a single random crash anyway.
It is, but I've never suffered from it.I thought the disable was to prevent the box getting stuck in a crash/reboot loop
You'll have to accept that your plugins may get disabled if there is a crash shortly after boot then. The presence of a crash message doesn't mean they have been though.So unless the disable function is considered of no value now (in which case let's lose it) I'd rather not disable it.
It was my suggestion of a counter, which is why I remembered it.I must have missed that one coming in.
humax ~ # diff /mod/boot/posttvcrash~ /mod/boot/posttvcrash --- /mod/boot/posttvcrash~ +++ /mod/boot/posttvcrash @@ -73,6 +73,7 @@ elif [ -z "$uptime" ] || [ "$uptime" -lt 60 ]; then if [ -f $ffile ]; then echo "Second fast crash - disabling plugins" + rm -f $ffile disable_plugins else echo "First fast crash"
if [ -f $ffile ]; then lct="`/bin/date -r $ffile '+%s'`" now="`/bin/date '+%s'`" [ $((now - lct)) -gt 300 ] && rm -f $ffile fi
That's right. You need two quick crashes (within the first minute following startup) to occur within 5 minutes of each other....is the consensus that disable now only happens if there are two early uptime crashes in quick succession? (so eg, one a day for a week wouldn't trigger disable.)