Hi
this is why you set group read/write permissions on everything. the
owner does not matter.
it does need some education on the user side, as some of the user groups
still assume that user permissions are the relevant thing, and act
accordingly.
JT
Simone Dalla Fina wrote:
> Thank you Marteen, I did -R with chmod but not with chown... Now I'm
> fixing it.
> Now each VO software dir is owned by <vo>sgm001. A CMS software manager
> (mapped as cmssgm003) is now not able to do some chmod because he's not
> the owner of the file. Could it be a problem (probably he don't need to
> chmod anymore)?
>
> Simone
>
> Maarten Litmaath wrote:
>> Simone Dalla Fina wrote:
>>
>>> Hi all,
>>>
>>> Recently we passed to pool accounts also for sgm and prd users.
>>> From that time on some software managers are not able to install
>>> properly their software on our exp_soft host.
>>>
>>> How may we set ownerships and permissions for each VO dir, subdirs and
>>> files?
>>>
>>> Currently we try to chown <vo>sgm001:<vo>sgm and chmod 775 but it's not
>>> the solution.
>> That should be sufficient. Did you use the "-R" option to those commands?
>> The chmod command should rather be this:
>>
>> chmod -R g+w $VO_theVO_SW_DIR
>>
>> What errors do the software managers get?
>>
>> Also check the ownership and permissions under /opt/edg/var/info for the
>> publication of the software tags.
|