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

[GRASS GIS]

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

Comment (by wenzeslaus):

 My current understanding is that that `clean_temp` is called in `grass.py`
 right when it checks if it determines that it is not a new user which is
 taken as a reason to clean the current mapset. Unfortunately the current
 mapset is the last used mapset, not necessarily the one requested. The
 mapset locking happens later on and only after that we can clean the
 mapset. Therefore, I will move  the `clean_temp` call only after the lock.

 Note: There is another `clean_temp` at the end. My assumption is that the
 start time one is meant to clean the mapset just in case.

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