Mikko Ohtamaa a écrit : >> What I did notice is that afterwards I could not shut down my zope >> instance anymore. I started it on the foreground, then changed >> something to cause a reload and then I could not use CTRL-C anymore to >> stop the instance. I had to use kill. > >> I take it collective.autorestart does not work when starting the >> instance on the foreground? > > It works when started in the foreground mode. > > However, this is a known issue (README.txt). I don't know what's > causing in and it doesn't happen all the time. > > - Monitor thread ends up to foobar state blocking the process from dying > > - inotify ends up to a foobar state blocking the process from dying > > I am not OS expert so I fixing this is not on very high priority. > > -Mikko > > _______________________________________________ > Product-Developers mailing list > [email protected] > http://lists.plone.org/mailman/listinfo/product-developers
Just to let you know that it s not sometimes but every time that i got stuck and must kill the zope instance. Nevertheless, it sounds encouraging, and it may worth the kill -9 ;) Something that can encourage you to fix your annoying deadlock is that i have integrated, but disabled by default your package in minitage's plone template :). One blocker can be that you have a thead in a infinite loop when the program shuts down preventing it to finnish, events may be good to trigger that . I didn't look at the implementation, it's just a thought. -- -- Cordialement, KiOrKY GPG Key FingerPrint: 0x1A1194B7681112AF
signature.asc
Description: OpenPGP digital signature
_______________________________________________ Product-Developers mailing list [email protected] http://lists.plone.org/mailman/listinfo/product-developers
