[GRASS-dev] GRASS resets group access rights
Maciej Sieczka
tutey at o2.pl
Sun Jul 20 12:58:44 EDT 2008
Glynn Clements pisze:
> Maciej Sieczka wrote:
>> Now edit the data as user2 and see the group write rights are
>> removed:
>>
>> $ ls -lr vector/pokrycie_przyborow_u65_10k
>> dbf/pokrycie_przyborow_u65_10k.dbf -rw-r--r-- 1 user2 users-grass
>> 375 2008-07-02 19:14 dbf/pokrycie_przyborow_u65_10k.dbf
>>
>> vector/pokrycie_przyborow_u65_10k: razem 140 -rw-r--r-- 1 user2
>> users-grass 1949 2008-07-02 19:14 topo -rw-rw---- 1 user1
>> users-grass 3402 2008-07-02 19:13 hist -rw-rw---- 1 user1
>> users-grass 176 2008-07-02 19:14 head -rw-rw---- 1 user1
>> users-grass 75 2008-07-02 19:14 dbln -rw-rw---- 1 user1
>> users-grass 116326 2008-07-02 19:14 coor -rw-r--r-- 1 user2
>> users-grass 349 2008-07-02 19:14 cidx
> Right; the top and cidx files are replaced with new files,
As well as the dbf file it seems - right?
> while the others are edited in-place.
>> As you can see although 2 different users (members of the same
>> group) edit the file, permissions were not changed. Yet in GRASS
>> they are. Is this OK?
> Not really. How to handle this situation will need to be resolved if
> and when we actually decide to remove the restriction that GRASS
> doesn't allow you to modify other users' files. Until then, the goal
> should be to determine why that restriction isn't being honoured, and
> how to fix it.
For now I put 'umask 7' into my grass64 executable, which forces access
rights I desire for files newly created by GRASS.
Maciek
--
Maciej Sieczka
www.sieczka.org
More information about the grass-dev
mailing list