I would agree with Anand that it's better to set up a cron job to run every minute or so and hit a url that returns some status (or logs the status to a file). This is what I've done in the past. I'd also put the cron job (or Windows Scheduled Task) on a different machine.
The best way to see if a web server is running properly is to fetch a url. A background process that logs something might tell you if the process is running but it won't tell you if the server is accepting requests. On Mar 12, 8:07 pm, Anand Chitipothu <anandol...@gmail.com> wrote: > తేదిన 12 మార్చి 2012 10:23 ఉ, Patrick Dunnigan > <patrick.m.dunni...@gmail.com> వ్రాశారు: > > > The point is to log a heartbeat from the running web.py process. > > > If the web.py server goes down, the heartbeat gets stale and actions can be > > taken. > > You can write a handler for /heartbeat and call it from a cronjob > periodically. > > Anand -- You received this message because you are subscribed to the Google Groups "web.py" group. To post to this group, send email to webpy@googlegroups.com. To unsubscribe from this group, send email to webpy+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/webpy?hl=en.
