2010-11-02, 15:24
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.
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.