2010-12-29, 00:30
It looks like local policy is preventing you from modifying the file.
In order to preserve MythTV's ownership of the file, mythicalLibrarian's logging and overall security of the system, the best way is to have user mythtv control all aspects of mythicalLibrarian's operation. For this reason, mythicalSetup asks you for a password for user mythtv. This makes user mythtv a full-fledged valid user on your system.
When running as user rmikulec, file operations and logging are performed by that username rather then mythtv. The linux filesystem's granular control can be a burden sometimes. It's simpler to simply not deal with that and allow mythtv to control it's files by running mythicalLibrarian as mythtv. User jobs are automatically run with mythtv permissions. Under most distributions, MythTV is run with mythtv permssions, however some distributions use other usernames, so I could not make it manditory for the user mythtv to be used. Because of Linux's granular permissions, and local policy preventing certain actions on different distributions, multiple users creating multiple files with different permissions is impossible to manage. The way around this is to bypass all of linux security, run as root or allow sudo with no password... However this is bad procedure and allows for a gigantic security hole.
It's always best if the user who creates the file, manages the file. In this case it's mythtv.
You can run
Let me know if there are any other problems.
In order to preserve MythTV's ownership of the file, mythicalLibrarian's logging and overall security of the system, the best way is to have user mythtv control all aspects of mythicalLibrarian's operation. For this reason, mythicalSetup asks you for a password for user mythtv. This makes user mythtv a full-fledged valid user on your system.
When running as user rmikulec, file operations and logging are performed by that username rather then mythtv. The linux filesystem's granular control can be a burden sometimes. It's simpler to simply not deal with that and allow mythtv to control it's files by running mythicalLibrarian as mythtv. User jobs are automatically run with mythtv permissions. Under most distributions, MythTV is run with mythtv permssions, however some distributions use other usernames, so I could not make it manditory for the user mythtv to be used. Because of Linux's granular permissions, and local policy preventing certain actions on different distributions, multiple users creating multiple files with different permissions is impossible to manage. The way around this is to bypass all of linux security, run as root or allow sudo with no password... However this is bad procedure and allows for a gigantic security hole.
It's always best if the user who creates the file, manages the file. In this case it's mythtv.
You can run
Code:
mythicalLibrarian --undo
sudo su mythtv
mythicalLibrarian --scan mpg /path_to_my/recordings
Let me know if there are any other problems.