id,summary,reporter,owner,description,type,status,priority,milestone,component,version,resolution,keywords,cc,platform,cpu
755,trying to start in mapset you don't own gives wrong error msg,hamish,grass-dev@lists.osgeo.org,"Hi,

if I do ""chmod 999.999 $LOCATION/user1"" to make my user account not the owner of a mapset, and then start grass with the full path to the mapset I get this error:

{{{
Cleaning up temporary files ...
Starting GRASS ...
$LOCATION/user1/.gislock: Permission denied
ERROR: $GISBASE/etc/lock:
hamish is currently running GRASS in selected mapset (file $LOCATION/user1/.gislock found). Concurrent use not allowed.
}}}


user1 is drwxr-xr-x, so the Permission denied comes from the fact that etc/lock can't write the .gislock file, not that my current user account already has a copy there. (I checked, the file doesn't exist)

So that Permission denied needs to be better caught I guess.
or improve  G!__mapset_permissions() or G!__mapset_permissions2() and it's a case of the error message being a bit too overenthusiastic?


if I start GRASS with -tcltk the mapset is simply missing from the list (greyed out would be nicer if $MAPSET/WIND exists but we don't own it). I don't have wx on this machine to test the wxGUI startup, nor did I test changing mapsets with g.mapset. And no idea what happens if you force the mapset change with g.gisenv.


Hamish
",defect,closed,minor,6.4.0,Default,svn-develbranch6,fixed,mapset access,,Linux,x86-32