[GRASS-user] Read only mapsets

[Markus Metz]

On Fri, Apr 26, 2019 at 3:59 PM Moritz Lennert <mlennert at club.worldonline.be>
wrote:
>
> On 26/04/19 11:53, Panagiotis Mavrogiorgos wrote:
> > Hello everyone,
> >
> > I was wondering, is there a way to enforce a Mapset to be read-only? I
> > guess that this can always be enforced on the Filesystem level with
> > something like this:
> >
> >     find . -type f -exec chmod a-w {} \;
> >
> >
> > but then again some file might need to be writable afterall (sqlite.db?)
> >
> > So is there a way to e.g. open specific maps in read-only mode?
>
> Normally, you can only write in a mapset if you are the owner of that
> mapset, so you could create a mapset owned by a "readonly" user/group.

Moreover, within a GRASS session, i.e. with GRASS tools, all mapsets but
the current mapset are readonly, that is, you can read data from other
mapsets but not modify them, even if the current user is also the owner of
other mapsets.

Markus M
>
> Moritz
> _______________________________________________
> grass-user mailing list
> grass-user at lists.osgeo.org
> https://lists.osgeo.org/mailman/listinfo/grass-user
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.osgeo.org/pipermail/grass-user/attachments/20190426/445f5ad6/attachment.html>