#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 annakrat):
Replying to [comment:6 annakrat]:
> I just tried this python
[http://code.activestate.com/recipes/278731-creating-a-daemon-the-python-
way/ recipe] and it worked for me, the processes are terminated. I tried
to find the difference and it seems that just this line is enough (in the
GuiModuleMain function):
>
> {{{
> --- core/utils.py (revision 58561)
> +++ core/utils.py (working copy)
> @@ -1064,7 +1064,8 @@
> child_pid = os.fork()
> if child_pid == 0:
> mainfn()
> - os._exit(0)
> + else:
> + os._exit(0)
> else:
> mainfn()
>
> }}}
>
> Can I apply it safely or can it cause some other troubles?
Soeren had the same idea (r58580). Unfortunately, I can't say it's solved
completely. I have still problem with g.gui.timeline. The subprocesses
don't terminate when it's called with parameter input or when it's called
without any parameter but then you display the dataset. When it's just
opened and closed the subprocesses terminate. For g.gui.animation it's
seems ok now. So I am confused what's different in g.gui.timeline. Well,
at least some progress...
--
Ticket URL: <http://trac.osgeo.org/grass/ticket/2151#comment:7>
GRASS GIS <http://grass.osgeo.org>
_______________________________________________
grass-dev mailing list
[email protected]
http://lists.osgeo.org/mailman/listinfo/grass-dev
