Marco Pasetti wrote: > > IIRC, if you just set GIS_LOCK (to anything) in init.bat, g.mapset > > will work. On Windows, the etc/lock program always succeeds (after > > printing a warning), so it's up to you to ensure that you don't run > > multiple GRASS sessions concurrently in the same mapset. > > at the moment I don't have GRASS installed on this machine, so I cannot > check it, but IIRC the .gislock file was not created, even if I added > GIS_LOCK=0 in the init.bat;
Correct. > that missing causes a problem when trying to close a mapset. What problem? g.mapset just calls remove() on the old mapset's .gislock file; it doesn't even check the return value, let alone complain. etc/lock just prints a warning then exits with a success status. init.sh unconditionally removes the file with "rm -f", which doesn't care whether it actually exists. init.bat doesn't mention .gislock at all. AFAICT, nothing else even knows of that file. -- Glynn Clements <[EMAIL PROTECTED]> _______________________________________________ grass-dev mailing list grass-dev@lists.osgeo.org http://lists.osgeo.org/mailman/listinfo/grass-dev
