I may have made a mistake in sharing a root folder


#1

I created a root folder called /var/share to hold my shares on the primary file server. I created all my shares there and shared them as as needed. Everything was working great, until I added another share to share out read only access to the /var/share folder for backing it up.

Here is what my shares table looks like. The top one is the share in question.

So I have a couple questions…

Will this override all the permissions on all the other shares since this is the root folder for the other shares? (I think it already has and I am fixing it).
Can I delete this share without deleting the /var/share folder and all the files the other shares depend on?

See the pickle I am in? :frowning:

Thanks.


#2

Hello,

I don’t know which of the many attributes you have used to make /var/shares a ‘readonly’ share, and I don’t know which sharing protocols you are using at all. So I can only vagely guess what happened.

First of all, I would think the management framework would never recursively apply attributes to existing directories or files. And on the share level, the management framework won’t adjust settings of other shares even if their paths overlap. So I’d suppose the settings you made for the other shares are not lost or overwritten by anything.

If you have set the permissions for the share’s root directory (removed write or access permissions) then this could affect the accessibility of the directories inside. Just set the permissions back, this can help. For making a share read-only, better uncheck the ‘write acces for the XXX protocol’ permissions at the share level; this should not interfere with other shares.

If it’s not about the pure directory permissions, please tell something more about the way you have created the ‘backup’ share, and be a little more specific about the errors you’re seeing.

Regards,
Frank Greif.