[GRASS-dev] [GRASS GIS] #2151: g.gui.* modules which use temporal framework leave processes after exiting

[GRASS GIS]

#2151: g.gui.* modules which use temporal framework leave processes after exiting
--------------------------------------------+-------------------------------
 Reporter:  annakrat                        |       Owner:  grass-dev@…              
     Type:  defect                          |      Status:  new                      
 Priority:  normal                          |   Milestone:  7.0.0                    
Component:  Python                          |     Version:  svn-trunk                
 Keywords:  g.gui.animation, temporal, RCP  |    Platform:  Linux                    
      Cpu:  All                             |  
--------------------------------------------+-------------------------------

Comment(by wenzeslaus):

 Replying to [comment:3 huhabla]:
 > All the methods that i have tried are not working in case the GUI module
 uses {{{os.fork()}}} to start the module in the background.

 > Why do we need fork() at all? Unix already support job management in the
 shell and it does not work on windows?
 >

 The idea was to start the application in the background (r57388, r57370 -
 r57378 launch GUI in the background). There was also a discussion on the
 mailing list with reasoning that `g.gui.*` should behave in the same way
 as `g.gui`, that these (`g.gui*`) are special cases (''not able to find
 link now'').

 While [source:grass/trunk/gui/wxpython/core/utils.py#L1053  GuiModuleMain]
 is using Python `os.fork`, `g.gui` is using
 [source:grass/trunk/lib/gis/parser.c#L796 G_spawn] from `grass/spawn.h`.

 When the generated GUI for a module is shown (`v.pack` or `g.region
 --ui`), no special functionality is provided and it blocks terminal unless
 you use `&`.

 > If we really need it, can this be implemented in a better way?

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