Re: [cobalt-users] CMU Ownership Problem

[Jeff Bilicki <jeff@xxxxxxxxxxx>]

>>> I reported this a few weeks ago. Haven't heard anything. It makes a big mess. 
>>> Only solution I had was to change all groups back manually.
>>
>>Who did you did you report this to?
>>
>>The group permission should be correct, and with the sticky bit set, site
>>users should be able to modify/update files still.  
>>
>>Jeff-
> To Cobalt Support via the web form with a note to notify you. 
> Not sure if the sticky bit was set but site owners could not modify the existing files.
> Could you provide an exact example of the full group and user ownership with correct permissions
> for site directories and default subdirectories on both Raq3 and Raq4? 
> At one time Cobalt support had recommended chmod 2755 <sitenumber>

I guess this would be a problem if the permissions of the files are
644 and not 664.  Here is a quickie work around
$ cd /home/sites/<sitename>/web
$ find . -type f | xargs chmod 664
$ find . -type f -name "*\.cgi" | xargs chmod 775   
$ find . -type f -name "*\.pl" | xargs chmod 775   

I do understand that this is a very big limitation in CMU at the current time.
The next version of CMU architecture, which will be avalible for Qube2 => Qube
3 migrations soon, stores data about each individual file migrated and restores
correct ownership even when uid/gid number changes.