[GRASSLIST:3359] Allowing multiple users to access a mapset
pnorquist at sift.info
Wed May 5 17:52:20 EDT 2004
We have a script that starts GRASS for a given location, mapset, and
map, and runs r.profile to find the altitude for a given point.
We would like to allow any user on our system to run the script on a
particular map (non-concurrently). But we've run into problems when
a user that doesn't own the mapset tries to read from it. Does this
have to be the PERMANENT mapset? Only the owner/admin will be modifying
the map, everyone else would only read from it (assuming that r.profile
only requires reading; is this true?).
We've found some old GRASSlist messages about creating a new mapset
the location for each user, but it's not entirely clear to us how to go
about it--what has to be in place for a non-owner to be able to read
a mapset. Also, it looks like some people have tried to get around the
ownership issue by disabling the uid checks in G_mapset_permissions.
We would appreciate any help that anyone could give us.
Also there is a question about buffer checking:
From gisbase.c (admittedly in an old version):
sprintf(msg,_("MAPSET %s - permission denied"), mapset);
Do you know what the _() around the format string does? Does this
help with bounds checking?
One last question--
Since we are using only a small part of the GRASS functionality, is
some way for us to pare down our GRASS installation so it contains only
the commands we use, and takes up less space?
More information about the grass-user