It's a interesting question. If the cron processes are children of the the main process, then I'd vote for having the main process send a SIGTERM to each child and wait() for a reasonable length of time before giving up. Makes things easier to manage. Obviously, a cron process written by a user is free to ignore the signal, but IMHO it's asking for trouble to do so.
Cheers, Mike On Feb 1, 5:58 pm, mdipierro <[email protected]> wrote: > I notice that too but I cannot figure out why yet. > > I am not sure that killing the main web2py process should also kill > the cron processes. I think I know how to change that but I am not > sure what the preferred behavior should be. > > On Feb 1, 4:48 pm, MikeEllis <[email protected]> wrote: > > > One funniness remains. I can't kill the web2py process with -SIGTERM > > any more. Have break out the heavy artillery and use -9. Also, > > killing the web2py process doesn't croak the cron processes. Have to > > kill them individually. > > > Cheers, > > Mike > > > On Feb 1, 5:00 pm, Thadeus Burgess <[email protected]> wrote: > > > > we might have his admin password, but he doesn't have ssl!! :) > > > > -Thadeus > > > > On Mon, Feb 1, 2010 at 3:57 PM, mdipierro <[email protected]> wrote: > > > > 173.203.204.205 > > -- You received this message because you are subscribed to the Google Groups "web2py-users" group. To post to this group, send email to [email protected]. To unsubscribe from this group, send email to [email protected]. For more options, visit this group at http://groups.google.com/group/web2py?hl=en.
