[mythtv-users] [SOLVED] MythTV storage groups can't see 2nd hard drive

[JCF Junkmail]

Thanks Alex and Simon for the further clarification on my previous statement.  That's very good news for me as I really didn't want to go through changing my partition strategy.  Even more importantly, I learned something new.

Still need to get my head around some details.  For example, folders only allow for one group (I believe).  So my current plan of action is to set "/content" as something no one can write to (and possibly not read neither), just execute and assign it a group common to all users. Within there, set other folders with different groups assigned (with mythmedia being a separate one) and allowing more flexibility for the different purposes.
I'll do experiments this evening and report back.  Not so much for you guys who are so knowledgeable, but for the newbies reading this mailing list on the web.  From personal experience, I know that forums are brilliant. I've been able to teach myself how to build this box from scratch just by reading 2,3 year old posts, and now it's taking over the house (I may well call it Hal at some point in the future).

PS: Appologies for top-posting.

On 05/06/12 18:43, Alex Tomlins wrote:
>On 05/06/12 18:28, JCF Junkmail wrote:
>> David,
>> Thanks for your reply.  You are spot on.  The permissions for /content (as opposed to the sub-
>>folder) didn't include mythtv as user nor group.  I've changed this and now it is working! Thanks.
>>
>> Now I understand.  It seems MythTV developers expected me to give them the whole partition for 
>>exclusive MythTV use.  If I may say so, this aspect is not very well documented, really.  I know I 
>>can still put other stuff there. However, I don't feel comfortable giving permission to mythtv to 
>>access my other content. I know there are parameters for making sure some space is always left 
>>unused; and chances are the software will behave well and all, but it just feels wrong.  I will 
>>have to rethink my partition strategy accordingly.  Thanks for the enlightenment.
>>
>> PS: Thanks Mike<mtdean>  for you reply as well.  I didn't get to check the backend log yet as 
>>David's suggestion did the trick already. Cheers.
>>
>I don't think that's 100% accurate. All myth needs is the relevant 
>permissions to be able to write to the directory specified in the 
>storage group.  This means that the user running mythbackend (typically 
>mythtv) needs write permissions on the specified directory, and at least 
>execute permissions on all the parent directories.
>
>I didn't see the permissions for your content directory, but I guess 
>they didn't have the necessary permissions for the mythtv user to cd 
>into the directory (i.e. execute permissions).
>
>It shouldn't be necessary to dedicate the whole partition to mythtv.

On 05/06/12 18:46, Simon Hobson wrote:
>No, I don't believe that is correct.
>Myth must have read/write access to the storage directory, and 
>implicit in that requirement is that it must have execute access (I 
>think, not sure about read as well) to all directories in the path to 
>it.
>So, in order to access /content/myth, the myth user must have some 
>permissions to /content. The execute bit, when applied to 
>directories, gives permission to descend through that directory and 
>access stuff within it (assuming you know it's name and have 
>permissions on it) - but doesn't give you permission to list the 
>contents of the directory (that is given by the read bit).
>http://en.wikipedia.org/wiki/Filesystem_permissions#Traditional_Unix_permissions
>
>You are welcome to put other stuff under /content, and you do not 
>need to give Myth any access to it. Obviously, if you do that, then 
>you will be sharing the physical space.