Hi Henrik,

you wrote that we can use CLASS=... in hobbit-alerts.cfg (see your attached email).

But what is the right way to use this tag in hobbit-alerts.cfg? I didn't find anything in Hobbit man-pages.

Regards.

Massimo Morsiani Information Technology Dept.

Gilbarco S.p.a. via de' Cattani, 220/G 50145 Firenze, Italy tel: +39-055-30941 fax: +39-055-318603 email: massimo.morsiani at gilbarco.com web: http://www.gilbarco.it

-----Original Message----- From: Henrik Stoerner [mailto:henrik at hswn.dk] Sent: sabato 12 gennaio 2008 19.03 To: hobbit at hswn.dk Subject: Re: [hobbit] hosts wildcards in clients-local.cfg

On Sat, Jan 12, 2008 at 05:29:11PM +0000, Szymon Bakowski wrote:

...

On Thu, Jan 10, 2008 at 12:34:12PM +0000, Szymon.Bakowski (at) ladbrokes.co.uk wrote:

...

Just wanted to ask a quick question (went through the archive, but haven't found an answer for my question):

Is it possible to use host wildcards in clients-local.cfg file ? They do work for me for example in hobbit-clients.cfg but it seems that I can not make it work in clients-local.cfg. In hobbit-clients.cfg I am using for example as follows:

HOST=%www..\.foo\.com

but it doesn't work in clients-local.cfg.

No, you cannot.

The way around this is to use host "classes". The default class for a

...

host is the name of the operating system - that's why the "[linux]" and "[hpux]" etc. sections work. You can change the class of a host either by configuring it with the CLASS:classname setting in bb-hosts, or by specifying the class on the client when you start the Hobbit client.

It is a bit annoying that you cannot use regexp's in client-local.cfg. Might be something I change.

Thank you Henrik for your reply. Classes did help indeed. Can I use them in other config files like for example in hobbit-clients.cfg ?

Yes, both hobbit-clients.cfg and hobbit-alerts.cfg support a CLASS=... way of selecting hosts.

Regards, Henrik

To unsubscribe from the hobbit list, send an e-mail to hobbit-unsubscribe at hswn.dk

This message (including any attachments) contains confidential and/or proprietary information intended only for the addressee.
Any unauthorized disclosure, copying, distribution or reliance on the contents of this information is strictly prohibited and may constitute a violation of law. If you are not the intended recipient, please notify the sender immediately by responding to this e-mail, and delete the message from your system. If you have any questions about this e-mail please notify the sender immediately.