Posts: 1,722
Joined: Sep 2009
Reputation:
20
Thank you for your input Ubuntite. I will make the necessary corrections.
--doMaintenance will delete all mythicalLibrarian database folders which it has created. --undo will undo all actions mythicalLibrarian took on your filesystem. Then you --scan your video folder again, and mythicalLibrarian will rescan your library.
Keep in mind that if the information was not in theTvDb at the time, or you were offline during an operation, mythicalLibrarian may put your file in the --doover option. It knows when there should be information on theTvDb, but it was not able to find it.
Posts: 1,722
Joined: Sep 2009
Reputation:
20
SYMLINK=Disabled was logging things improperly. Please delete any doover.sh doover.sh.old, undo.sh or undo.sh.old files which are in your ~/mythicalLibrarian folder. Then update to the SVN.
I corrected all problems which were mentioned in your first post in SVN revisions 742 - 749. 750 addressed symlink=disabled issues. you will no longer generate an undo and you will generate doovers only for those files which mythicalLibrarian says should be --doover'd later.
Please test again and let me know about the python bindings issue. 0.24 has switched to python bindings because very soon, it will be impossible to perform a direct database search of MythTV. The MythTV devs will be changing their database significantly.
The python bindings abstract the database. From now on, MythTV Developers will support the connection to extract information rather then me worrying about having to rewrite my database extractor every time MythTV's version changes. I just have to support our MythDataGrabber python script, and that's the end of the worrying.
I would like to see mythicalDiagnostics final output regarding python bindings.
Posts: 1,722
Joined: Sep 2009
Reputation:
20
Generally, it's always best to run mythicalLibrarian as a single user at all times. In your case it would not matter much, as there does not need to be consistancy between MythTV and the generated files.
For --scan, it does not matter except that the showing will be created by one user and the accessory files and folders(folders, .NFOs and comskips) are created by another. That means the accessory files and folders will not be removed automatically until the user who created the files runs mythicalLibrarian again. It just throws off/delays file and folder tracking a bit.
for --doMaintenance, it must be run per user
I believe I've removed all issues with --update on multiple users. That is not an issue.
For --doover, it must be run per user
For --undo, it must be run per user
I can add some stars in the help files to denote the user dependent commands.
I've played around with the idea of a unified database and tracking. However, it would not work right for several reasons.
1. The log must be written every time by every user, it could be chmod'd 777
2. The folder.tracking and created.tracking would need to be chmod'd 777
3. Each created folder and each created file per database would need to be chmod'd 777
4. every comskip and MythTV recording would need to be chmod'd 777
5. If the user was to terminate early, or an error was experienced before the files were chmod'd mythicalLibrarian would cease to function for the next user, which would probly be mythtv.
There's more too.
I will update the help tonight. The wiki will require a rewrite on several sections within the next week.
Can you show me what the problem is with the python bindings? I would really like to make sure things are working as they should.
Posts: 72
Joined: Apr 2008
Reputation:
0
Another thing I am noticing is that before, when an Episode couldn't be identified by thetvdb.com, the file would be renamed to include the date it was recorded. Recently, that seems to be broken. Now Showings are named:
ShowName S0E0 ( Recorded on ).mpg
Also, the commercial skip file is not being created anymore...
Posts: 1,722
Joined: Sep 2009
Reputation:
20
I will check out the showings naming convention.
I am not reproduce any of the other issues. Did you try to remove it in mythicalSetup? Are those trailing /'s showing up in mythicalSetup? If they are there, then you should remove them. It sounds like you may not have database connectivity for the other issues.
As for the trailing /'s, mythicalSetup stores the last value used in the ~/.mythicalLibrarian/mythicalSetup folder. Whatever is put in the dialog box in mythicalSetup is what will be put into the built program.
Check your ~/.mythtv/mysql.txt file. The database defaults eg.. "Localhost=" is pulled from your ~/.mythtv/mysql.txt file, and dropped directly into the variable.
Run mythicalLibrarian --update twice, once to set the values and a second time to verify the proper things were put in the boxes.
I will add something which truncates any trailing /'s from mythicalSetup.
Posts: 72
Joined: Apr 2008
Reputation:
0
Also, it appears that recordings aren't being deleted and removed from the MythTV database after being moved according to SYMLINK=Disabled... This just recently started happening after upgrading to 750.
Posts: 1,722
Joined: Sep 2009
Reputation:
20
I fixed 2 problems based on your log.
1. It was finding "" which would get run though showtranslations and pick the first item.
2. additional test statement.
Lets see why you are not getting database information. It should help me to set things up for others.