bb-services feature request(s)

[Charles Jones <jonescr (at) cisco.com>]

1. It would be useful if you could use an EXEC keyword in bb-services, 
which would execute a shell script or program, which you could then 
parse the output.  This could be easier than having a server-side 
external script in some cases, and could also be used to handle 
difficult to check services, so you don't have to use arcade methods 
like the one used to check oratns (see bb-services [oratns] entry) . It 
would be assumed that if EXEC is used, no port number needs to be defined.

For example:

[pgpool]
   exec '/usr/bin/psql -U postgres -h dbpool -c "show pool_status" 
template1'
   expect "replication_enabled          | 1"

2. It would be nice if we could define multiple expect statements, and 
that it didn't matter where in the output the strings were.
For example:

[pgpool]
   exec '/usr/bin/psql -U postgres -h dbpool -c "show pool_status" 
template1'
   expect "replication_enabled          | 1"
   expect "server_status                | master(192.168.0.200 on 5432) 
up secondary(192.168.0.201 on 5432) up |"

3. It would be handy if we could use regular expressions in expect strings.
4. It would be cool if you could use an option to either show only the 
lines that matched "expect", or highlight them (bold?)
For example:
[pgpool]
   exec '/usr/bin/psql -U postgres -h dbpool -c "show pool_status" 
template1'
   expect "replication_enabled          | 1"
   expect "server_status                | master(192.168.0.200 on 5432) 
up secondary(192.168.0.201 on 5432) up |"
   options banner,highlight
or
[pgpool]
   exec '/usr/bin/psql -U postgres -h dbpool -c "show pool_status" 
template1'
   expect "replication_enabled          | 1"
   expect "server_status                | master(192.168.0.200 on 5432) 
up secondary(192.168.0.201 on 5432) up |"
   options showmatch

Just some ideas :-)

-Charles