And straight on to another question:
Is there a way of switching of the permissions check when opening a mapset? It prevents me from opening mapsets that are mounted on different filesystems as the grass installation. E.g. if I try to open a mapset located on a remote directory (mounted using fuse) in my local Ubuntu grass6.4 version fails with:
ERROR: MAPSET PERMANENT - permission denied
Any solution to this would be much appreciated.
Regards,
Michel
–
Am 31.07.2013 18:44, schrieb Michel Wortmann:
And straight on to another question:
Is there a way of switching of the permissions check when opening a
mapset? It prevents me from opening mapsets that are mounted on
different filesystems as the grass installation. E.g. if I try to open a
mapset located on a remote directory (mounted using fuse) in my local
Ubuntu grass6.4 version fails with:ERROR: MAPSET PERMANENT - permission denied
Any solution to this would be much appreciated.
I totally agree with you. Especially for the 1 machine with dual boot
set-up.
Unfortunately, core developers are of different opinion:
[Fwd: Re: GRASS permission issue]
http://thread.gmane.org/gmane.comp.gis.grass.devel/39132/focus=39146
Hope if more come in we could convince them...
Regards.
Michel Wortmann wrote:
And straight on to another question:
Is there a way of switching of the permissions check when opening a
mapset? It prevents me from opening mapsets that are mounted on
different filesystems as the grass installation. E.g. if I try to open a
mapset located on a remote directory (mounted using fuse) in my local
Ubuntu grass6.4 version fails with:ERROR: MAPSET PERMANENT - permission denied
Any solution to this would be much appreciated.
In any of the current SVN versions, setting the environment variable
GRASS_SKIP_MAPSET_OWNER_CHECK to any non-empty string will suppress
the check.
--
Glynn Clements <glynn@gclements.plus.com>
Michel Wortmann:
> And straight on to another question:
> Is there a way of switching of the permissions check when opening a
> mapset? It prevents me from opening mapsets that are mounted on
> different filesystems as the grass installation. E.g. if I try to open a
> mapset located on a remote directory (mounted using fuse) in my local
> Ubuntu grass6.4 version fails with:
>
> ERROR: MAPSET PERMANENT - permission denied
>
> Any solution to this would be much appreciated.
Tim Michelsen:
I totally agree with you. Especially for the 1 machine with dual boot
set-up.
Unfortunately, core developers are of different opinion:
[Fwd: Re: GRASS permission issue]
http://thread.gmane.org/gmane.comp.gis.grass.devel/39132/focus=39146Hope if more come in we could convince them...
Regards.
Tim,
I have never ever had such a "problem" -- it always was in the end a
permission issue on the "operating system world". That is, one has to
properly mount the drive/filesystem he wants to use under its own user-id (at
least in Linux) and there will be no issue.
Best regards, Nikos
ERROR: MAPSET PERMANENT - permission denied
Any solution to this would be much appreciated.
In any of the current SVN versions, setting the environment variable
GRASS_SKIP_MAPSET_OWNER_CHECK to any non-empty string will suppress
the check.
Yes, but what for the people who wanna rely on the precompiled packages?
And this could be a switch in the .grassrc or elsewhere.
ERROR: MAPSET PERMANENT - permission denied
Any solution to this would be much appreciated.
Glynn:
In any of the current SVN versions,
setting the environment variable GRASS_SKIP_MAPSET_OWNER_CHECK
to any non-empty string will suppress the check.
(that also includes 6.4.3-final by the way)
Tim:
Yes, but what for the people who wanna rely on the precompiled packages?
And this could be a switch in the .grassrc or elsewhere.
it still works at run time. you can make it locally permanent on a
single user setup with:
echo "export GRASS_SKIP_MAPSET_OWNER_CHECK=true" >> ~/.grass.bashrc
As with anything else, be sure to extra take care when disabling
safety mechanisms.
Hamish
ps- the build-time compiler flag version is "-DSKIP_MAPSET_OWN_CHK"