From: Zac Elston <zelston@...>
Date: 2007-04-12T05:30:25+09:00
Subject: Re: webrick w/ XML-RPC w/ xinetd

Brian Candler wrote:
> On Thu, Apr 12, 2007 at 12:43:39AM +0900, Zac Elston wrote:
>> /usr/lib/ruby/1.8/net/http.rb:1990:in `read_status_line': wrong status
>> line: "[2007-04-11 11:21:03] INFO  WEBrick 1.3.1" (Net::HTTPBadResponse)
> 
> As you've discovered, you can't run Webrick as an inetd service.
> 

I guess technically I did, but it's not going to do what I want :) 
indeed it was a silly way to manage a problem. I just made it a normal 
service and that works..I was looking for a way to manage the service, 
and xinetd was my first attempt.

> But do you have any particular reason *not* to use Webrick? 

only in theory, as I wasn't sure of the stability of the app.  this 
XML-RPC app needs to run constantly to provide status of the host.  I'll 
test it over the next week to see if it has issues with longevity.  it's 
not managing production traffic or anything, so this just responds 
whenever someone needs a status (ie, did my code push work 
ok...check..ok, thanks..sleep until next push..)  My main app is a rails 
thingy so I just tried the ruby XML-RPC code example as my first attempt 
for proof of concept.  a real C server should be the next gen of this 
"server monitor" to talk to the rails XML-RPC client.

that said...thanks for the refresher

-zaq

-- 
Posted via http://www.ruby-forum.com/.