I use supervisord because it brings the configuration of daemon services 
within a consistent configuration.

I can write one supervisord.conf, and so long as the supervisor is 
installed in any given distro, I can run my services. 

No need to then worry about upstart vs systemd vs SysV init vs ... whatever.

Plus, supervisor plays nice with python.

On Friday, 6 November 2015 13:47:07 UTC, Niphlod wrote:
>
> workers "check in" every heartbeat seconds. You can enable all sorts of 
> logs to trace the exact second they died.
>
> That being said, there's no way for a died process to check if it's alive. 
> That's why EVERY "daemon" should be handled by each platform's "daemon" 
> system (or a process specifically made for it): in windows it's nssm, on 
> unix it can be upstart or systemd, or a 3rd party solution like supervisord.
>
> On Friday, November 6, 2015 at 2:20:43 AM UTC+1, Benson Myrtil wrote:
>>
>> Good morning,
>>
>> I am sure this is a noob question but I cant seem to find a solid answer. 
>> I have started a worker nodes using the 'python web2py.py -K [app]' 
>> command. Everything appears to work fine for a while. My scheduled task 
>> need to run once a day but I am noticing that the worker node randomly 
>> 'dies' after a couple of hours.
>>
>> Is there some setting I am missing to prevent the worker nodes from dying 
>> even if they are idle for several hours?
>>
>

-- 
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.

Reply via email to