[GRASS-dev] [GRASS GIS] #613: clean_temp: not safe for concurrent use

GRASS GIS trac at osgeo.org
Sat Sep 15 20:46:05 PDT 2018


#613: clean_temp: not safe for concurrent use
----------------------+--------------------------------------
  Reporter:  hamish   |      Owner:  grass-dev@…
      Type:  defect   |     Status:  closed
  Priority:  normal   |  Milestone:  7.6.0
 Component:  Startup  |    Version:  6.4.0 RCs
Resolution:  fixed    |   Keywords:  clean_temp init grass.py
       CPU:  All      |   Platform:  All
----------------------+--------------------------------------
Changes (by wenzeslaus):

 * status:  new => closed
 * resolution:   => fixed


Comment:

 In [changeset:"73342" 73342]:
 {{{
 #!CommitTicketReference repository="" revision="73342"
 init: clean mapset only after locking it (fixes #613, see #1286)

 Only after we set the user-requested mapset as current (GISRC) and lock
 it,
 we can do the startup cleaning using clean_temp (to clean after previous
 sessions
 if needed).

 The cleaning was in place at least since r11260 but it got moved to a
 wrong place some
 time after that but before r37863.
 }}}

-- 
Ticket URL: <https://trac.osgeo.org/grass/ticket/613#comment:5>
GRASS GIS <https://grass.osgeo.org>



More information about the grass-dev mailing list