#226: WinGRASS fails to create .gislock opening a mapset
----------------------------+-----------------------------------------------
Reporter: msieczka | Owner: grass-dev@…
Type: defect | Status: new
Priority: major | Milestone: 6.4.2
Component: Default | Version: svn-develbranch6
Keywords: wingrass, qgis | Platform: MSWindows XP
Cpu: All |
----------------------------+-----------------------------------------------
Comment(by mmetz):
IIUC, the .gislock file is not created under windows because kill() does
not exist under windows, used by find_process().
Under Linux, assume the following scenario: a group of people are working
from different machines on the same location, different mapsets. The
location is on a network drive accessible by everyone. Now g.mapset
mapset=othermapset using lock (GIS_LOCK) checks if it could kill the pid
written in .gislock. But if the pid in .gislock has been written by a
different machine/system, then the pid in .gislock has nothing to do with
the pid's available to lock, and the kill()-test is complete moot. Right?
In this case it would be more helpful if .gislock would not hold a pid,
but the name of the user, e.g. user@host, currently accessing the mapset.
Therefore I would suggest to skip the find_process() step and assume that
a mapset is locked as long as the file .gislock exists. And always, also
on windows, write the file .gislock.
Markus M
--
Ticket URL: <http://trac.osgeo.org/grass/ticket/226#comment:11>
GRASS GIS <http://grass.osgeo.org>
_______________________________________________
grass-dev mailing list
[email protected]
http://lists.osgeo.org/mailman/listinfo/grass-dev
