Re: Features...

[Martin Pala]

Christian Hopp wrote:

> Hi!
>
> Here are some features for discussion...
>
> 1) Generic protocol test...
>
>   if failed port 1234 [{expect|send} "string" [{expect|send} "string"] ...]
>
>   Actually it is quite self explaining...  for every "send" the
>   "string" is sent through the connection (w/ or w/o ssl), and for
>   every "expect" the return is read and matched against the "string".
This seems good :) Maybe only instead of "send" we can use already 
present "request" word, which serves for the same purpose in already 
implemented protocol tests (such as http).

> 2) A watchdog thread... (I think I have mentioned this hidden
>   somewhere in a mail some days ago)
>
>   We detach the validation as one thread, then we do already have the
>   http thread and whatever might come.  The main thread become the
>   watchdog.  After each validation and after each accept (w/ or w/o
>   timeout) both do set a semaphore which is checked by the watchdog.
>   In case one of them has not done this the thread is restarted or
>   monit is restarted.
I'm not sure whether it is needed to separate main thread for watchdog. 
It could be usefull to watch httpd thread, but i think it could be 
implemented inside of main thread. As workaround in the case that monit 
httpd availability is issue, it can be monitored by present monit 
version from main thread by:

check host monit-httpd with address 127.0.0.1
  if failed port 2812 protocol http then exec "/usr/bin/monit -c 
/etc/monitrc reload"

This is not exactly the same thing as httpd thread watchdog, but it can 
solve the issue too. In the case that monit httpd is not accessible, 
monit will reload itself, which will cause failed thread to start.


> 3) Auth via htpasswd...
>
>   auth /path [user, ...]
>
>   where "path" is the fq path it the corresponding htpasswd and
>   "user" is a user grant access.  If user is omitted all users do have
>   access.
>
> CHopp
>
>  
This can be usefull :)

Martin