Opened 5 years ago

Closed 5 years ago

Last modified 5 years ago

#11148 closed Bug Report - General (fixed)

PingHost setting in config.xml does not work

Reported by: vah78@… Owned by: wagnerrp
Priority: minor Milestone: 0.26.1
Component: MythTV - General Version: 0.26
Severity: medium Keywords: ping PingHost config.xml
Cc: Ticket locked: no


The pinging of the mysql server at program (mythbackend, mythfrontend, mythlogserver, etc.) start cannot be disabled with this setting. This is a problem when mysql is running on a different host and ping is either not installed or does not work as a non-root user. Thus, ping fails and programs starts to prompt connection settings from the user.

I did reconfigure using the command line prompts with mythbackend and GUI prompts with mythfrontend, and both correctly(?) saved the setting as "<PingHost?>0</PingHost?>" to config.xml, but it does not stop them from trying to ping when started next time.

Tested on Arch Linux with MythTV version 0.26 from community repository. (This did work up to version 0.25.2 but that probably still used the old mysql.txt even though it created a config.xml in ~/.mythtv.)

As a workaround, a dummy shell script as the ping command in user's path will do the trick: #!/bin/sh exit 0

Attachments (0)

Change History (3)

comment:1 Changed 5 years ago by wagnerrp

  • Milestone changed from unknown to 0.26.1
  • Owner set to wagnerrp
  • Status changed from new to assigned

comment:2 Changed 5 years ago by Raymond Wagner <rwagner@…>

  • Resolution set to fixed
  • Status changed from assigned to closed

In 65a720c9b830ab77bbd2931e03fb428e05dee6f9/mythtv:

Read in dbPingHost value from config.xml.

Fixes #11148

comment:3 Changed 5 years ago by Raymond Wagner <rwagner@…>

In 4c67cedbea9e4b18d7688f30af02bd46e65cd07d/mythtv:

Read in dbPingHost value from config.xml.

Fixes #11148
(cherry picked from commit 65a720c9b830ab77bbd2931e03fb428e05dee6f9)

Add Comment

Modify Ticket

as closed The owner will remain wagnerrp.
The resolution will be deleted. Next status will be 'new'.

E-mail address and user name can be saved in the Preferences.

Note: See TracTickets for help on using tickets.