<div class="gmail_quote"><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
BTW it works like a charm and now I can see my myth recordings on my<br>
XP laptop -- woohooo....<br>
<br>
Here is an updated version of the code with some minor usability<br>
enhancements:<br></blockquote></div><br>Great timing (for me)! I just got my new laptop running last night and fired up myth FE only to realize that I'd have to spend ages getting the settings cloned from my existing FE before I'd be happy using it. :( Then I found this thread, thanks! Haven't run it yet but I will when I get home.<br>
<br>I'm interested in the delete hostname function since I happen to have a few leftover invalid entries in my DB from changing my hostname without doing it the "mythtv way".<br><br>I'm not very familiar with mysql but I'd like to make the following suggestions that I think would go really nicely with the current functions:<br>
1) list all hostnames that have some configuration info in the DB. This will let people like me clean up after their mistakes more easily using your delete hostname command. :)<br>2) grant privileges to user@hostname (or user@"192.168.1.%" or some other wildcard for home networks) to allow the new FE to connect to the DB since by default only mythtv@localhost is allowed. The syntax for this is shown on this wiki <a href="http://www.mythtv.org/wiki/MythFrontend">http://www.mythtv.org/wiki/MythFrontend</a> <br>
3) similar to delete hostname: revoke privileges to users/hostnames that were added by mistake. After way too long online I cobbled together the following commands for example:<br>use mysql;<br>select HOST, User from user; [to show my mistakes like adding username=oops]<br>
show grants for oops@"localhost"; [check that the user doesn't have access to mysql for some app other than mythtv]<br>delete from user where host = "localhost" and user = "oops"; [clean up entries]<br>
<br>Hmm #3 seems to involve more human interaction and double checking than I'd really suggest for a script... perhaps that one's a bad idea? At least now I'll have those commands saved in this thread.<br><br>
I still think that #1 would be great and perhaps #2 could be added as a function within the copy hostname? That way the new hostname is completely ready to go after the copy.<br><br>cheers,<br>Matt<br><br>