Opened 10 years ago
Closed 6 years ago
#2678 closed defect (wontfix)
GRASS starts even when Mapset is locked
Reported by: | wenzeslaus | Owned by: | |
---|---|---|---|
Priority: | normal | Milestone: | 7.0.7 |
Component: | Startup | Version: | svn-trunk |
Keywords: | init, grass.py, lock, locking, .gislock, GUI | Cc: | |
CPU: | Unspecified | Platform: | Linux |
Description
When GUI is requested and location provided, GRASS starts even when location is locked.
Start GRASS in one terminal:
grass71 [.../grassdata/nc_spm_08_grass7/user1]
Start GRASS in another terminal, specify (the same) mapset in command line and ensure you start GUI:
grass71 .../grassdata/nc_spm_08_grass7/user1 -gui
This behavior is already present in r65235 (source:grass/trunk/lib/init/grass.py?rev=65235#L884).
For 7.0 branch it might be enough to just call exit after showing the error message in GUI. However, for trunk, there are some related refactoring and interface changes which would be good to do.
What needs to be changes is here:
- trunk source:grass/trunk/lib/init/grass.py#L1128
- 70 branch: source:grass/branches/releasebranch_7_0//lib/init/grass.py#L882
Note that for debugging the grass.py
you can use GRASS_DEBUG
variable set to something.
Change History (8)
comment:1 by , 9 years ago
Milestone: | 7.0.1 → 7.0.2 |
---|
comment:5 by , 9 years ago
Milestone: | 7.0.4 → 7.0.5 |
---|
comment:6 by , 8 years ago
Milestone: | 7.0.5 → 7.0.6 |
---|
comment:7 by , 7 years ago
Milestone: | 7.0.6 → 7.0.7 |
---|
Ticket retargeted after 7.0.1 milestone closed