Changing file-permissions

[markus.doits@…]

(a mail about this issue has also been sent to the mythtv-user-mailing list: ​http://mythtv.org/pipermail/mythtv-users/2009-May/256245.html)

I'm using Debian Sqeeze/Sid and the mythtv-backend runs as a user "mythtv", the frontend as my regular user.

Files (recordings) get saved on /mnt/recordings/mythtv, which is a local mounted filesystem (ext4). user:group of this dir is mythtv:mythtv and files created by the backend usually get permission 644. since my local user is also in the group "mythtv", everything works well (so even a 640 would be enough). but here's the first problem: sometimes a file is created with permissions 600. this happens to recordings, live-tv-files and even transcoded files (.nuv). playing them in mythfrontend is not possible and i have to chmod 644 them manually - which sucks having to do so every time. i searched for that problem by google a few times already and found only one post saying to restart mythtv-backend and new files will again have 644. this works, until the issue happens again... is there anything i can to to force permission 644 on newly created files? the file-permission should be constant at least, not changing from time to time.

[Dibblah]

Not a mythtv issue.

[markus.doits@…]

mythbackend (and/or mythtranscode) create(s) files with inconsistent permissions. i'm not sure whether this is intended (what is the logic behind then?), but i think all recordings created by mythtv should have the same permissions.

if it's not mythtv managing the permissions of files, how do files get any permission? (i think a simple "chmod 644" (or whatever it should be) after creating any recording, transcoded file, ... would solve this problem). maybe umask-handling in mythtv is simply broken (sometimes changed, sometimes default) and chmod would be a workaround-hack until someone investigates this problem further. it's a minor problem then, but nevertheless a bug...