[mythtv-users] hostname problem in MythArchive

John Pilkington J.Pilk at tesco.net
Tue Aug 28 16:19:34 UTC 2012


On 27/08/12 23:53, John Pilkington wrote:
> Since installing 0.25-fixes on my main box I've had problems with
> MythArchive.  I think this may be because the config settings are
> defined by the frontend but are being read using the hostname of the
> backend.  The lines in the mythburn.py script read
>
> DB = MythTV.MythDB()
> configHostname = DB.gethostname()
>
> I've tried a direct hack in mythburn.py that looked hopeful.  What would
> be the way of getting the frontend's 'Custom Identifier' from the DB
> instead?
>

OK, it works for me (in creation of a playable DVD) if the 'Custom 
identifier' from Frontend Setup > General > page 2 is used as 
configHostname.

If defined it's LocalHostName in ~/.mythtv/mysql.txt.  Isn't that the 
file that's being phased out?  config.xml doesn't have it and I haven't 
found it in the DB.

I suspect this is also the cause of the lack of a progress log in 
'Create an Archive' mode, Ticket #10505, but I don't think that's done 
through mythburn.py and my hack doesn't change it.  A usable Archive is 
created.

A warning: while I was investigating this, a chmod called within 
mythburn.py walked recursively all over my home directory.  I've 
commented that line out.  There are some multi-delete sections too...

John P




More information about the mythtv-users mailing list