well, on unix python docs report that p.terminate() use sigkill, so I wonder why in your env one works and not the other...
On Friday, November 4, 2016 at 8:57:34 AM UTC+1, Erwn Ltmann wrote: > > BTW: if I use os.kill(p.pid,signal.SIGKILL) instead of p.termiate() > everithing is fine. > > 11-04 08:40:59.521 [13556] web2py.Scheduler - DEBUG - MD: terminating (os >> kill) >> 11-04 08:40:59.521 [13556] web2py.Scheduler - DEBUG - MD: terminated >> 11-04 08:40:59.522 [13556] web2py.Scheduler - DEBUG - MD: joining >> 11-04 08:40:59.524 [13556] web2py.Scheduler - DEBUG - MD: joined >> > > No running and still waiting processes are left. :) > > But, if I configure timeouts longer then 30 seconds - maybe 10 minutes or > more, then the worker is still waiting until this timeout. Because of that > I have to find the reason for sem_wait(). > > Erwn > -- Resources: - http://web2py.com - http://web2py.com/book (Documentation) - http://github.com/web2py/web2py (Source code) - https://code.google.com/p/web2py/issues/list (Report Issues) --- You received this message because you are subscribed to the Google Groups "web2py-users" group. To unsubscribe from this group and stop receiving emails from it, send an email to web2py+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
