[Top][All Lists]
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: is monit just a pain in the arse or what ?
From: |
Jan-Henrik Haukeland |
Subject: |
Re: is monit just a pain in the arse or what ? |
Date: |
Fri, 27 Jul 2007 22:47:01 +0200 |
On 27. jul. 2007, at 21.16, andrew taylor wrote:
no one has yet to explain why a running monit daemon refuses to
respond to a "monit summary" request...
So what does the following ruby on-liner print?
ruby -r socket -e 's=TCPSocket.new("localhost",2812);s.send("GET /
HTTP/1.0\r\nAuthorization: Basic YWRtaW46dGVzdA==\r\n\r\n",0);s.each{|
r|r=="\r\n"?exit : puts(r);}'
Please use admin:test as username:password in monitrc for the
authorization header to work.
Re: is monit just a pain in the arse or what ?, Jan-Henrik Haukeland, 2007/07/27
Re: is monit just a pain in the arse or what ?, andrew taylor, 2007/07/27
Re: is monit just a pain in the arse or what ?, Alexey Zilber, 2007/07/27