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
Cpu almost pegged out at 100% when TVH connection is lost for whatever reason.
Just tested: pidvbip idle (not subscribed), shutdown TVH daemon, cpu to 100% on pi and stays there. Start TVH daemon, pi still at 100% cpu load. Cannot restart subscription.
So need some form of hts timeout/socket timeout.
(noted here mainly to remind myself to look into it!)
The text was updated successfully, but these errors were encountered:
Thanks, yes. This has been in the back of my mind for a while - yes, we should have a timeout, and then pidvbip should attempt to reconnect at regular intervals (no idea what, perhaps 5 or 10 seconds?)
You may perhaps want to hold off until I've finished implementing multiple-server support in pidvbip - I'm most of the way there, so should hopefully finish in the next few days.
Cpu almost pegged out at 100% when TVH connection is lost for whatever reason.
Just tested: pidvbip idle (not subscribed), shutdown TVH daemon, cpu to 100% on pi and stays there. Start TVH daemon, pi still at 100% cpu load. Cannot restart subscription.
So need some form of hts timeout/socket timeout.
(noted here mainly to remind myself to look into it!)
The text was updated successfully, but these errors were encountered: