Opened 17 years ago

Closed 16 years ago

#3279 closed patch (duplicate)

Improve server reconnect/wakeup method

Reported by: anonymous Owned by: Isaac Richards
Priority: minor Milestone: unknown
Component: mythtv Version: head
Severity: medium Keywords: wakeup reconnect connect timeout server context
Cc: mythtv-dev@… Ticket locked: no

Description

This patch improves the server reconnect attempt used in mythcontext.

A mythbusydialog is displayed while myth is trying to connect rather than just appearing with a blank background and a log message (dialog is disabled when a mythcontext server connection is made without a gui - eg. with mythshutdown).

The reconnect algorithm is adjusted such that:

  1. Wakeup command is executed.
  2. Myth attempts to open a connection to the backend once every second until the reconnect timeout occurs or a connection is established.
  3. If the reconnect timeout is reached, the wakeup command will be issued again (as before), unless the max number of attempts have been executed.

This is more efficient than before, where the reconnect attempt would not retry until the next wake command is executed.

Attachments (2)

backend_connect.diff (2.9 KB) - added by devel@… 17 years ago.
Mythcontext server reconnect improvements
backend-reconnect-180707.diff (2.9 KB) - added by devel@… 17 years ago.
updated patch for server reconnect

Download all attachments as: .zip

Change History (4)

Changed 17 years ago by devel@…

Attachment: backend_connect.diff added

Mythcontext server reconnect improvements

Changed 17 years ago by devel@…

updated patch for server reconnect

comment:1 Changed 16 years ago by Matthew Wire <devel@…>

This is included as part of #4184 which extends the backend reconnect function that mythtv-setup can be configured to start/stop the backend and different commands are used depending on whether the master backend is local or not.

As such, this ticket can be closed.

comment:2 Changed 16 years ago by paulh

Resolution: duplicate
Status: newclosed

Replaced by #4184

Note: See TracTickets for help on using tickets.