On my system (debian) and on Dreamhost, I ended up with a ton of mail
when I did that... Curl sends back a response report to cron which sends
it to your mail drop.
So even though the output is suppressed, the report isn''t.
Easy fix:
0-59/5 * * * * curl -s -r 0-99
http://somedomain.com>/dev/null>/dev/null
-----Original Message-----
From: rails-bounces@lists.rubyonrails.org
[mailto:rails-bounces@lists.rubyonrails.org] On Behalf Of Steve Ross
Sent: Wednesday, February 22, 2006 12:27 PM
To: rails@lists.rubyonrails.org
Subject: [Rails] [Tip] Keeping fastcgi in memory
There has been discussion about using wget and curl to ping a server
every 5 minutes or so to keep the fastcgi processes alive. I didn''t
find
a command line for this so I thought I''d post one.
Put this in your crontab using crontab -e or your favorite other method:
0-59/5 * * * * curl -r 0-99 http://somedomain.com>/dev/null 2>/dev/null
This hits the default page of somedomain.com every 5 minutes and dumps
the output into a black hole. If you''re lucky and have an HTTP 1.1
compliant version of curl, you will only yank 100 bytes of the page.
n.b., the page you hit should not be cached or it will bypass Rails and
serve up the static page.
Cheers
--
Posted via http://www.ruby-forum.com/.
_______________________________________________
Rails mailing list
Rails@lists.rubyonrails.org
http://lists.rubyonrails.org/mailman/listinfo/rails