"Tom Metro" <[EMAIL PROTECTED]> wrote in message news:[EMAIL PROTECTED] > Joel Melohn wrote: >> I believe that you need write permission if you want to use all the >> features >> available such as scheduling recordings. > > I wasn't aware you could do scheduling from mvpmc. > > If you can, someone really needs to add something to the wiki, as a > search for "schedule" or "scheduling" turns up nothing. > > > Don Bossung wrote: >> mvpmc needs access to the server that holds the mythtv database using the >> default database that mythtv uses with the default username and default >> password for that user. >> >> mythconverg is the default database name for mythtv >> mythtv are the default password and user for the database. >> >> Now if you changed your username and password during install, you would >> have >> to modify them here. > > I don't know if this is an aspect of the Ubuntu packaging, but on my > MythTV installation, a random password was generated. Does the SVN > version of MythTV or older versions actually use "mythtv" as the > password? (I suppose if you're not using an installer, it's up to you to > create the password.) > > >> So the parameters for your command line become >> mvpmc -y 12.34.56.78 -s 98.76.54.32 -T mythconverg -u mythtv -p mythtv & > > My guess is that in a typical setup, -p would be the only parameter > needed for MySQL access. (Providing the code doesn't disable MySQL > access if one or more of the other parameters are absent. As they all > have defaults, I'd assume not.) > > >> 12.34.56.78 is the server that holds the database >> 98.76.54.32 is the server that is running mythtv >> NOTE: these two could/would be the same if you have only one mythtv >> server. > > Per the code -y defaults to the value of -s, or 'localhost'. (I'm not > sure how useful 'localhost' would ever be for mvpmc, except when running > in an emulator.) > > > I've updated the wiki to reflect the defaults specified in the code: > http://mvpmc.wikispaces.com/commandline > > I also added a link to main.c in the Git repository as the place to find > defaults. I'd like to see us do more of this in the wiki, so when the > documentation doesn't go into enough depth or goes out of date, the next > person that comes along knows where to look to find the definitive > information, and might even update the wiki. > > >> When you setup mvpmc with these parmeters, I believe that it DOES use the >> mythtv protocol, but maybe someone else can shed some light on this. > > My understanding was that the direct database access was used for the > experimental live TV capability. MythTV protocol is used for everything > else. I don't have the database access set up on my mvpmc, and it seems > to do everything except the new live TV. > > -Tom
Tom I guess seeing the 'Schedule Recordings' and 'Find Program' on the MythTV menu led me to find the scheduling capabilities of mvpmc. I have always used mythtv on fedora and the yum install mythtv-suite sets up and installs the packages. With this, the database name has always been mythconverg, username mythtv and password mythtv. These have always been the values in the mythfrontend as well. Personally, I don't like to rely on defaults and have a tendecy to specify the options I need. Just me. Thanks for the link to the .c code though. ------------------------------------------------------------------------- This SF.net email is sponsored by DB2 Express Download DB2 Express C - the FREE version of DB2 express and take control of your XML. No limits. Just data. Click to get it now. http://sourceforge.net/powerbar/db2/ _______________________________________________ Mvpmc-users mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/mvpmc-users mvpmc wiki: http://mvpmc.wikispaces.com/
