October 2005 - Xymon - Xymon mailman web

bb-dftab
by mccoupe1＠hotmail.com 14 Oct '05

14 Oct '05

Hey all, I'm trying to set up a number of mount points to be monitored. I've already moved the bb-dftab.DIST to bb-dftab on the client (both client and server are RH Linux) and made the edits in the described format of /abc/123:xx:yy. I've also tried it including the localhost at the start of each line as well. However after restarting the client I'm still not seeing the mount points being monitored in the server. Everything else that the client is monitoring seems to be working properly, including all of my customizations like additional processes and adjusted thresholds. I've even tried running 'bb' on the server and dropping the disk test so I could start cleanly but to no avail. I'm not seeing anything in the BBOUT files either. Does anyone have any ideas? Thanks, Mark Coupe Commonwealth of Massachusetts

1 0

[hobbit] Hobbit client checks
by Larry.Barber＠usda.gov 14 Oct '05

14 Oct '05

How about just putting an "include" mechanism in the configuration file reader? Then you would just need to create an account for each system's administrator on the Hobbit server, they could create configuration files for their boxes and then the Hobbit administrator could just include them into the master configuration file. Thanks, Larry Barber On Fri, 2005-10-14 at 03:37 -0500, henrik at hswn.dk wrote: > On Fri, Oct 14, 2005 at 09:37:53AM +0200, Dirk Kastens wrote: > > > > "All configuration of disk thresholds, load limits, which > > processes to monitor etc. is done on the Hobbit server, > > NOT on the client. This is to allow centralized configuration > > of the monitoring system." > > > > I think, this is not a good idea. I told the administrators > > of the client systems that they are responsible for what > > BB will monitor. If they install a new program, they have > > to add the process name to the bb-proctab file to check > > if it's running. Now they have to inform me about what > > should be monitored and I have to edit the hobbit-clients.cfg > > file. That's a lot of work, apart from the fact that the > > file will be growing very quickly. > > It's a design decision I made. The distributed configuration > doesn't work for my setup; I am sure you can find people > who prefer each of the setups. > > > Wouldn't it be possible to still use local configuration > > files that are located in the client/etc directory? > > Not the way Hobbit is built currently. So if that is a > problem, stick with the BB client for now. > > It wouldn't be impossible to support both models. What currently > happens is that the client data is sent to the Hobbit server; > here it is fed into the hobbitd_client module and converted into > cpu, disk, memory etc. status messages. These are then sent > back to the Hobbit server. > > So the simplest solution would be to run the normal Hobbit client > on your servers, but instead of sending data directly to the > Hobbit server, it would be fed into a local hobbitd_client > running on the monitored server. This does require some small > code changes in the hobbitd_client module, but not very much. > > > Regards, > Henrik > > > To unsubscribe from the hobbit list, send an e-mail to > hobbit-unsubscribe at hswn.dk > > >

1 0

post tag.
by tlp-hobbit＠holme-pedersen.dk 14 Oct '05

14 Oct '05

How can I make the post content collumn go red if the http server is not resonding ? Now I get a clear image but I would like the test to go red. /Thomas

2 2

Hobbit client checks
by Dirk.Kastens＠uni-osnabrueck.de 14 Oct '05

14 Oct '05

Hi, "All configuration of disk thresholds, load limits, which processes to monitor etc. is done on the Hobbit server, NOT on the client. This is to allow centralized configuration of the monitoring system." I think, this is not a good idea. I told the administrators of the client systems that they are responsible for what BB will monitor. If they install a new program, they have to add the process name to the bb-proctab file to check if it's running. Now they have to inform me about what should be monitored and I have to edit the hobbit-clients.cfg file. That's a lot of work, apart from the fact that the file will be growing very quickly. Wouldn't it be possible to still use local configuration files that are located in the client/etc directory? Best wishes, Dirk

2 1

funny errors in the logs and weird random http monitoring failures
by pbliss＠techvalleycom.com 14 Oct '05

14 Oct '05

Hello all, At risk of covering an already well worn topic (I did check the archives first, I swear) I'm getting two strange behaviors that may be related. I've inherited a Hobbit server that was working fine until the unit was reset (rudely), and since then it's been working but has been a little funky. In my bb-display.log and bb-network I see: 2005-10-11 16:10:39 Could not connect to bbd at 127.0.0.1:1984 - Connection refused 2005-10-11 16:10:39 Whoops ! bb failed to send message - Connection failed 2005-10-11 16:10:39 hobbitd status-board not available 2005-10-11 16:10:39 Could not connect to bbd at 127.0.0.1:1984 - Connection refused 2005-10-11 16:10:39 Whoops ! bb failed to send message - Connection failed 2005-10-11 16:10:43 Could not connect to bbd at 127.0.0.1:1984 - Connection refused 2005-10-11 16:10:43 Whoops ! bb failed to send message - Connection failed 2005-10-11 16:10:43 hobbitd status-board not available 2005-10-11 16:10:43 Could not connect to bbd at 127.0.0.1:1984 - Connection refused 2005-10-11 16:10:43 Whoops ! bb failed to send message - Connection failed When I do a "netstat -anp" I do see Proto Recv-Q Send-Q Local Address Foreign Address State PID/Program name tcp 0 0 0.0.0.0:1984 0.0.0.0:* LISTEN 6237/hobbitd So I'm not sure what gives. It also doesn't seem to be a consistent condition. Also, perhaps related, I have a few servers in my bb-hosts file that are configured to check http which go into alarm for periods for no apparent reason. I'm obviously pretty new to Hobbit, so any pointers would be GREATLY appreciated. Thanks! -Paul

4 6

Alert Syntax and Notification log mismatch
by iqbala-hobbit＠qwestip.net 13 Oct '05

13 Oct '05

Hi All I did a bbcmd hobbit_alert --dump-config and looked for particular host testhost1 HOST=%.* EXHOST=%testhost1(.*) MAIL sysadmin at here.net,oncall at here.net FORMAT=TEXT REPEAT=30 SERVICE=msgs DURATION>10 HOST=%testhost1(.*) EXSERVICE="msgs,vmio" MAIL sysadmin at here.net,oncall at here.net FORMAT=TEXT REPEAT=30 MAIL user at here.com,123456789 at skytel.com FORMAT=TEXT REPEAT=30 HOST=%testhost1(.*) SERVICE="vmio" MAIL sysadmin at here.net FORMAT=TEXT REPEAT=30 DURATION>10 HOST=%testhost2(.*)|testhost1(.*) SERVICE="msgs" SCRIPT /export/home/hobbit/server/bin/script user at here.com,12345678 at skytel.com FORMAT=TEXT REPEAT=30 So only sysadmin at here.net and oncall at here.net should get any alert related to testhost1.here.net's vmio service. But I am seeing user at here.com and 123456789 at skytel.com are also getting those alerts per my notification log (hobbit)@hobbitserver:~/server/etc$ tail -100 /var/log/hobbit/notifications.log Wed Oct 12 09:23:33 2005 testhost1.here..net.vmio (1.2.1.251) sysadmin at here.net,oncall at here.net 1129123412 0 Wed Oct 12 09:23:35 2005 testhost1.here.net.vmio (1.2.1.251) user at here.com,12345678 at skytel.com 1129123412 0 Thu Oct 13 09:23:48 2005 testhost1.here..net.vmio (1.2.1.251) sysadmin at here.net,oncall at here.net 1129209826 0 Thu Oct 13 09:23:50 2005 testhost1.here.net.vmio (1.2.1.251) user at here.com,12345678 at skytel.com 1129209826 0 Any help to demystify this would be appreciated I am using 4.1.2 for hobbit server and BB 1.9c for testhost1.here.net Thanks -- Asif Iqbal PGP Key: 0xE62693C5 KeyServer: pgp.mit.edu "..there are two kinds of people: those who work and those who take the credit...try to be in the first group;...less competition there." - Indira Gandhi

2 2

PCRE reference with examples
by rsmrcina＠wi.rr.com 13 Oct '05

13 Oct '05

Is there an online reference for PCRE available, including examples? I'm having difficulty setting up alerts and I clearly need help with PCRE. Thanks. -- Rich Smrcina VM Assist, Inc. Main: (262)392-2026 Cell: (414)491-6001 Ans Service: (360)715-2467 rich.smrcina at vmassist.com Catch the WAVV! http://www.wavv.org WAVV 2006 - Chattanooga, TN - April 7-11, 2006

4 10

[hobbit] hobbitd status-board not available
by David.Gore＠mci.com 13 Oct '05

13 Oct '05

What does this message mean. Typically we get this when disabling multiple hosts. Is it a host resource issue, something isn't replying quick enough? We are on the snapshot from 03 October. This has been happening over many weeks and different snapshots. OS is solaris 9. It really is starting to frustrate people when we have a maintenance and everyone gets repeated pages during the maintenance. I am pretty sure these happen as people disable hosts and it fails although bb2.html shows them going to blue in the history, they will not show up on the enable/disable screen and usually show as failed when executing the disable. I did get disable to work after I restarted hobbit, but less than 12 hours later it is failing again. Here are some logs: bb-display.log: 2005-09-28 01:19:22 hobbitd status-board not available 2005-09-28 01:38:47 hobbitd status-board not available 2005-09-28 19:57:51 hobbitd status-board not available 2005-09-28 20:01:53 hobbitd status-board not available 2005-09-29 03:00:01 hobbitd status-board not available 2005-09-29 19:50:052005-09-30 00:14:10 hobbitd status-board not available 2005-09-30 00:15:12 hobbitd status-board not available 2005-09-30 00:16:13 hobbitd status-board not available 2005-09-30 04:15:17 hobbitd status-board not available 2005-10-06 21:37:08 hobbitd status-board not available 2005-10-07 20:43:13 hobbitd status-board not available 2005-10-07 21:41:15 hobbitd status-board not available 2005-10-08 02:56:16 hobbitd status-board not available 2005-10-08 04:11:19 hobbitd status-board not available 2005-10-08 04:12:20 hobbitd status-board not available 2005-10-08 15:22:32 hobbitd status-board not available 2005-10-08 15:32:34 hobbitd status-board not available 2005-10-08 15:40:36 hobbitd status-board not available history.log: 2005-10-08 15:29:28 Will not update /export/home/hobbit/data/hist/thisHost1.memory - color unchanged (blue) 2005-10-08 15:29:28 Will not update /export/home/hobbit/data/hist/thisHost1.procs - color unchanged (blue) 2005-10-08 15:29:28 Will not update /export/home/hobbit/data/hist/thisHost1.msgs - color unchanged (blue) 2005-10-08 15:29:28 Will not update /export/home/hobbit/data/hist/thisHost1.cpu - color unchanged (blue) 2005-10-08 15:29:28 Will not update /export/home/hobbit/data/hist/thisHost1.se - color unchanged (blue) 2005-10-08 15:29:28 Will not update /export/home/hobbit/data/hist/thisHost1.prtdiag - color unchanged (blue) 2005-10-08 15:29:28 Will not update /export/home/hobbit/data/hist/thisHost1.disk - color unchanged (blue) 2005-10-08 15:29:28 Will not update /export/home/hobbit/data/hist/thisHost1.conn - color unchanged (blue) 2005-10-08 15:31:40 Will not update /export/home/hobbit/data/hist/anotherHost01.memory - color unchanged (blue) 2005-10-08 15:31:40 Will not update /export/home/hobbit/data/hist/anotherHost01.prtdiag - color unchanged (blue) 2005-10-08 15:31:40 Will not update /export/home/hobbit/data/hist/anotherHost01.se - color unchanged (blue) 2005-10-08 15:31:40 Will not update /export/home/hobbit/data/hist/anotherHost01.procs - color unchanged (blue) 2005-10-08 15:31:40 Will not update /export/home/hobbit/data/hist/anotherHost01.msgs - color unchanged (blue) 2005-10-08 15:31:40 Will not update /export/home/hobbit/data/hist/anotherHost01.cpu - color unchanged (blue) 2005-10-08 15:31:40 Will not update /export/home/hobbit/data/hist/anotherHost01.disk - color unchanged (blue) 2005-10-08 15:31:40 Will not update /export/home/hobbit/data/hist/anotherHost01.conn - color unchanged (blue) 2005-10-08 15:31:40 Will not update /export/home/hobbit/data/hist/anotherHost01b.conn - color unchanged (blue) 2005-10-08 15:31:40 Will not update /export/home/hobbit/data/hist/anotherHost02.oradb - color unchanged (blue) 2005-10-08 15:31:40 Will not update /export/home/hobbit/data/hist/anotherHost02.orasys - color unchanged (blue) 2005-10-08 15:31:40 Will not update /export/home/hobbit/data/hist/anotherHost02.conn - color unchanged (blue) 2005-10-08 15:31:40 Will not update /export/home/hobbit/data/hist/anotherHost02.procs - color unchanged (blue) 2005-10-08 15:31:40 Will not update /export/home/hobbit/data/hist/anotherHost02.memory - color unchanged (blue) 2005-10-08 15:31:40 Will not update /export/home/hobbit/data/hist/anotherHost02.disk - color unchanged (blue) 2005-10-08 15:31:40 Will not update /export/home/hobbit/data/hist/anotherHost02.cpu - color unchanged (blue) 2005-10-08 15:31:40 Will not update /export/home/hobbit/data/hist/anotherHost02.se - color unchanged (blue) 2005-10-08 15:31:40 Will not update /export/home/hobbit/data/hist/anotherHost02.prtdiag - color unchanged (blue) 2005-10-08 15:31:40 Will not update /export/home/hobbit/data/hist/anotherHost02.msgs - color unchanged (blue) 2005-10-08 15:31:40 Will not update /export/home/hobbit/data/hist/anotherHost02b.conn - color unchanged (blue) 2005-10-08 15:31:40 Will not update /export/home/hobbit/data/hist/anotherHost03.topology - color unchanged (blue) 2005-10-08 15:31:40 Will not update /export/home/hobbit/data/hist/anotherHost03.memory - color unchanged (blue) 2005-10-08 15:31:40 Will not update /export/home/hobbit/data/hist/anotherHost03.prtdiag - color unchanged (blue) 2005-10-08 15:31:40 Will not update /export/home/hobbit/data/hist/anotherHost03.net2 - color unchanged (blue) 2005-10-08 15:31:40 Will not update /export/home/hobbit/data/hist/anotherHost03.se - color unchanged (blue) 2005-10-08 15:31:40 Will not update /export/home/hobbit/data/hist/anotherHost03.conn - color unchanged (blue) 2005-10-08 15:31:40 Will not update /export/home/hobbit/data/hist/anotherHost03.msgs - color unchanged (blue) 2005-10-08 15:31:40 Will not update /export/home/hobbit/data/hist/anotherHost03.cpu - color unchanged (blue) 2005-10-08 15:31:40 Will not update /export/home/hobbit/data/hist/anotherHost03.disk - color unchanged (blue) 2005-10-08 15:31:40 Will not update /export/home/hobbit/data/hist/anotherHost03b.conn - color unchanged (blue) 2005-10-08 15:38:23 Will not update /export/home/hobbit/data/hist/thisHost1.memory - color unchanged (blue) 2005-10-08 15:38:23 Will not update /export/home/hobbit/data/hist/thisHost1.procs - color unchanged (blue) 2005-10-08 15:38:23 Will not update /export/home/hobbit/data/hist/thisHost1.msgs - color unchanged (blue) 2005-10-08 15:38:23 Will not update /export/home/hobbit/data/hist/thisHost1.cpu - color unchanged (blue) 2005-10-08 15:38:23 Will not update /export/home/hobbit/data/hist/thisHost1.se - color unchanged (blue) 2005-10-08 15:38:23 Will not update /export/home/hobbit/data/hist/thisHost1.prtdiag - color unchanged (blue) 2005-10-08 15:38:23 Will not update /export/home/hobbit/data/hist/thisHost1.disk - color unchanged (blue) 2005-10-08 15:38:23 Will not update /export/home/hobbit/data/hist/thisHost1.conn - color unchanged (blue) 2005-10-08 15:38:23 Will not update /export/home/hobbit/data/hist/thisHost2.memory - color unchanged (blue) 2005-10-08 15:38:23 Will not update /export/home/hobbit/data/hist/thisHost2.se - color unchanged (blue) 2005-10-08 15:38:23 Will not update /export/home/hobbit/data/hist/thisHost2.prtdiag - color unchanged (blue) 2005-10-08 15:38:23 Will not update /export/home/hobbit/data/hist/thisHost2.procs - color unchanged (blue) 2005-10-08 15:38:23 Will not update /export/home/hobbit/data/hist/thisHost2.msgs - color unchanged (blue) 2005-10-08 15:38:23 Will not update /export/home/hobbit/data/hist/thisHost2.cpu - color unchanged (blue) 2005-10-08 15:38:23 Will not update /export/home/hobbit/data/hist/thisHost2.linkstate - color unchanged (blue) 2005-10-08 15:38:23 Will not update /export/home/hobbit/data/hist/thisHost2.disk - color unchanged (blue) 2005-10-08 15:38:23 Will not update /export/home/hobbit/data/hist/thisHost2.conn - color unchanged (blue) 2005-10-08 15:39:59 Will not update /export/home/hobbit/data/hist/anotherHost01.memory - color unchanged (blue) 2005-10-08 15:39:59 Will not update /export/home/hobbit/data/hist/anotherHost01.prtdiag - color unchanged (blue) 2005-10-08 15:39:59 Will not update /export/home/hobbit/data/hist/anotherHost01.se - color unchanged (blue) 2005-10-08 15:39:59 Will not update /export/home/hobbit/data/hist/anotherHost01.procs - color unchanged (blue) 2005-10-08 15:39:59 Will not update /export/home/hobbit/data/hist/anotherHost01.msgs - color unchanged (blue) 2005-10-08 15:39:59 Will not update /export/home/hobbit/data/hist/anotherHost01.cpu - color unchanged (blue) 2005-10-08 15:39:59 Will not update /export/home/hobbit/data/hist/anotherHost01.disk - color unchanged (blue) 2005-10-08 15:39:59 Will not update /export/home/hobbit/data/hist/anotherHost01.conn - color unchanged (blue) 2005-10-08 15:39:59 Will not update /export/home/hobbit/data/hist/anotherHost01b.conn - color unchanged (blue) 2005-10-08 15:39:59 Will not update /export/home/hobbit/data/hist/anotherHost02.oradb - color unchanged (blue) 2005-10-08 15:39:59 Will not update /export/home/hobbit/data/hist/anotherHost02.orasys - color unchanged (blue) 2005-10-08 15:39:59 Will not update /export/home/hobbit/data/hist/anotherHost02.conn - color unchanged (blue) 2005-10-08 15:39:59 Will not update /export/home/hobbit/data/hist/anotherHost02.procs - color unchanged (blue) 2005-10-08 15:39:59 Will not update /export/home/hobbit/data/hist/anotherHost02.memory - color unchanged (blue) 2005-10-08 15:39:59 Will not update /export/home/hobbit/data/hist/anotherHost02.disk - color unchanged (blue) 2005-10-08 15:39:59 Will not update /export/home/hobbit/data/hist/anotherHost02.cpu - color unchanged (blue) 2005-10-08 15:39:59 Will not update /export/home/hobbit/data/hist/anotherHost02.se - color unchanged (blue) 2005-10-08 15:39:59 Will not update /export/home/hobbit/data/hist/anotherHost02.prtdiag - color unchanged (blue) 2005-10-08 15:39:59 Will not update /export/home/hobbit/data/hist/anotherHost02.msgs - color unchanged (blue) 2005-10-08 15:39:59 Will not update /export/home/hobbit/data/hist/anotherHost02b.conn - color unchanged (blue) 2005-10-08 15:39:59 Will not update /export/home/hobbit/data/hist/anotherHost03.topology - color unchanged (blue) 2005-10-08 15:39:59 Will not update /export/home/hobbit/data/hist/anotherHost03.memory - color unchanged (blue) 2005-10-08 15:39:59 Will not update /export/home/hobbit/data/hist/anotherHost03.prtdiag - color unchanged (blue) 2005-10-08 15:39:59 Will not update /export/home/hobbit/data/hist/anotherHost03.net2 - color unchanged (blue) 2005-10-08 15:39:59 Will not update /export/home/hobbit/data/hist/anotherHost03.se - color unchanged (blue) 2005-10-08 15:39:59 Will not update /export/home/hobbit/data/hist/anotherHost03.conn - color unchanged (blue) 2005-10-08 15:39:59 Will not update /export/home/hobbit/data/hist/anotherHost03.msgs - color unchanged (blue) 2005-10-08 15:39:59 Will not update /export/home/hobbit/data/hist/anotherHost03.cpu - color unchanged (blue) 2005-10-08 15:39:59 Will not update /export/home/hobbit/data/hist/anotherHost03.disk - color unchanged (blue) 2005-10-08 15:39:59 Will not update /export/home/hobbit/data/hist/anotherHost03b.conn - color unchanged (blue) ~David To unsubscribe from the hobbit list, send an e-mail to hobbit-unsubscribe at hswn.dk

2 5

[hobbit] PCRE reference with examples
by rsmrcina＠wi.rr.com 13 Oct '05

13 Oct '05

Thanks Larry, Dan and Henrik! Larry.Barber at usda.gov wrote: > No \s is typically used to indicate whitespace in regexp's. \w usually > matches alphanumeric characters and the underscore character, hence Rich > probably wants something like: > > HOST=%^va\w* > > % - required by Hobbit to indicate the start of a regexp > ^ - start of line character > \w - matches any alphanumeric/underscore character > * - 0 or more \w's > > You can add a $ to the end of the line, but it won't change anything > since the * will grab all the characters to the end of the line anyway, > assuming that they are all alphanumeric and that Hobbit strips off all > the leading and trailing whitespace. > > Thanks, > Larry Barber > > On Thu, 2005-10-13 at 11:02 -0500, henrik at hswn.dk wrote: > >>On Thu, Oct 13, 2005 at 10:50:26AM -0500, Rich Smrcina wrote: >> >>>Ok, that's great info. Thanks! >>> >>>Based on that I'm ending up with an expression like: >>> >>>HOST=$va[\d\w]*$ >>> >>>To match any host beginning with 'va' that has zero or more >> >>alphanumeric >> >>>characters after it. Is there an easier way to write this? If >> >>not >> >>>that's fine, I just want to make sure I'm using it correctly. >> >>I'd say >> HOST=%^va[\d]*$ >> >>You need the "%" first, to tell Hobbit that what comes next is a >>regexp. >>Then the "^" means that the expression must match at the beginning of >>the string. "\w" is whitespace ? Think so - in that case it is not >>needed, since Hobbit will never match with any whitepace in the >>hostname. >> >> >>>Another poster (Asif Iqbal) posted the MAIL directives with >> >>multiple >> >>>recipients. Does that work like he posted? Can the multiple >> >>email >> >>>recipients be put into a macro? Consider the following: >>> >>>$pg-tom=(tomsemail at somewhere.com|tomscell at wireless.com) >>>HOST=tomshost >>> MAIL $pg-tom DURATION=5m COLOR=red >> >>What comes after the MAIL keyword is passed directly to your "mail" >>utility. So it would probably be better to have >> >> $pg-tom=tomsemail at somewhere.com,tomscell at wireless.com >> >>if your "mail" tool supports listing multiple recipients separated by >>commas. Some dont - then you can use a short-hand notation like: >> >> $pg-tom=tomsemail at somewhere.com tomscell at wireless.com >> >>and separate them by spaces - Hobbit will handle this as if you had >>multiple "MAIL ..." lines with each of the mail recipients. So it >>sends >>out the mail in separate e-mails, instead of one e-mail to all of the >>recipients. (Same net effect). >> >> >>One more thing: I'm sure "DURATION=5m" is not what you want. Make >>that >>"DURATION>5m". >> >> >> >>Regards, >>Henrik >> >> >>To unsubscribe from the hobbit list, send an e-mail to >>hobbit-unsubscribe at hswn.dk >> >> >> > > > > > To unsubscribe from the hobbit list, send an e-mail to > hobbit-unsubscribe at hswn.dk > > > -- Rich Smrcina VM Assist, Inc. Main: (262)392-2026 Cell: (414)491-6001 Ans Service: (360)715-2467 rich.smrcina at vmassist.com Catch the WAVV! http://www.wavv.org WAVV 2006 - Chattanooga, TN - April 7-11, 2006

1 0

[hobbit] PCRE reference with examples
by Larry.Barber＠usda.gov 13 Oct '05

13 Oct '05

No \s is typically used to indicate whitespace in regexp's. \w usually matches alphanumeric characters and the underscore character, hence Rich probably wants something like: HOST=%^va\w* % - required by Hobbit to indicate the start of a regexp ^ - start of line character \w - matches any alphanumeric/underscore character * - 0 or more \w's You can add a $ to the end of the line, but it won't change anything since the * will grab all the characters to the end of the line anyway, assuming that they are all alphanumeric and that Hobbit strips off all the leading and trailing whitespace. Thanks, Larry Barber On Thu, 2005-10-13 at 11:02 -0500, henrik at hswn.dk wrote: > On Thu, Oct 13, 2005 at 10:50:26AM -0500, Rich Smrcina wrote: > > Ok, that's great info. Thanks! > > > > Based on that I'm ending up with an expression like: > > > > HOST=$va[\d\w]*$ > > > > To match any host beginning with 'va' that has zero or more > alphanumeric > > characters after it. Is there an easier way to write this? If > not > > that's fine, I just want to make sure I'm using it correctly. > > I'd say > HOST=%^va[\d]*$ > > You need the "%" first, to tell Hobbit that what comes next is a > regexp. > Then the "^" means that the expression must match at the beginning of > the string. "\w" is whitespace ? Think so - in that case it is not > needed, since Hobbit will never match with any whitepace in the > hostname. > > > Another poster (Asif Iqbal) posted the MAIL directives with > multiple > > recipients. Does that work like he posted? Can the multiple > email > > recipients be put into a macro? Consider the following: > > > > $pg-tom=(tomsemail at somewhere.com|tomscell at wireless.com) > > HOST=tomshost > > MAIL $pg-tom DURATION=5m COLOR=red > > What comes after the MAIL keyword is passed directly to your "mail" > utility. So it would probably be better to have > > $pg-tom=tomsemail at somewhere.com,tomscell at wireless.com > > if your "mail" tool supports listing multiple recipients separated by > commas. Some dont - then you can use a short-hand notation like: > > $pg-tom=tomsemail at somewhere.com tomscell at wireless.com > > and separate them by spaces - Hobbit will handle this as if you had > multiple "MAIL ..." lines with each of the mail recipients. So it > sends > out the mail in separate e-mails, instead of one e-mail to all of the > recipients. (Same net effect). > > > One more thing: I'm sure "DURATION=5m" is not what you want. Make > that > "DURATION>5m". > > > > Regards, > Henrik > > > To unsubscribe from the hobbit list, send an e-mail to > hobbit-unsubscribe at hswn.dk > > >

1 0