Xymon Mailing List Archive search

Question about CLASS= & classname

3 messages in this thread

list Steve Aiello · Thu, 13 Jul 2006 09:52:12 -0400 ·
Per the hobbit-clients.cfg documentation I read the following:
    CLASS=classname Rule match by the client class-name. You specify
    the class-name for a host when starting the client through the
    "--class=NAME" option to the runclient.sh script. If no class is
    specified, the host by default goes into a class named by the
    operating system.

My questions:
The default classname setting of the operating system, which value is it
? When I look at the client data of a host I see the following:
   [uname]
   Linux serverName 2.6.16-gentoo-r7 i686
   [osversion]
   Gentoo Base System version 1.6.14

Is the default value of classname set to [uname] or [osversion]. Also is
it the full name ? If so do I define my CLASS="Linux serverName
2.6.16-gentoo-r7 i686" ? Can regular expresion be used, CLASS=%Linux.* ?

Can a host be defined to more than one class, i.e.
   1.2.3.4   serverName   # ssh CLASS:Linux CLASS:webServer

If a host can have more than one class definition, what happens when you
get CLASS configuration parameter collision ?

Also, it may bee helpful to have the Info report show which class the
device falls under.

Thank you,
  Steve
list Steve Aiello · Fri, 21 Jul 2006 07:39:30 -0400 ·
Was just curious if anyone had any information, or docs I missed that
details CLASS= more.

Thanks,
quoted from Steve Aiello
-----Original Message-----
From: Aiello, Steve (GE, Corporate, consultant) Sent: Thursday, July 13, 2006 9:52 AM
To: 'user-ae9b8668bcde@xymon.invalid'
Subject: Question about CLASS= & classname


Per the hobbit-clients.cfg documentation I read the following:
    CLASS=classname Rule match by the client class-name. You specify
    the class-name for a host when starting the client through the
    "--class=NAME" option to the runclient.sh script. If no class is
    specified, the host by default goes into a class named by the
    operating system.

My questions:
The default classname setting of the operating system, which value is it ? When I look at the client data of a host I see the following:
   [uname]
   Linux serverName 2.6.16-gentoo-r7 i686
   [osversion]
   Gentoo Base System version 1.6.14

Is the default value of classname set to [uname] or [osversion]. Also is it the full name ? If so do I define my CLASS="Linux serverName 2.6.16-gentoo-r7 i686" ? Can regular expresion be used, CLASS=%Linux.* ?

Can a host be defined to more than one class, i.e.
   1.2.3.4   serverName   # ssh CLASS:Linux CLASS:webServer

If a host can have more than one class definition, what happens when you get CLASS configuration parameter collision ?

Also, it may bee helpful to have the Info report show which class the device falls under.

Thank you,
  Steve
list Henrik Størner · Fri, 11 Aug 2006 15:25:36 +0200 ·
Hi Steve,
quoted from Steve Aiello

On Thu, Jul 13, 2006 at 09:52:12AM -0400, Aiello, Steve (GE, Corporate, consultant) wrote:
Per the hobbit-clients.cfg documentation I read the following:
    CLASS=classname Rule match by the client class-name. You specify
    the class-name for a host when starting the client through the
    "--class=NAME" option to the runclient.sh script. If no class is
    specified, the host by default goes into a class named by the
    operating system.

My questions:
The default classname setting of the operating system, which value is it ?
It's the value of $BBOSTYPE which gets setup by the Hobbit client
environment. It's basically defined at compile-time. There's a list of
the OS names near the beginning of the lib/misc.c file in the Hobbit 
source; I should probably document that somewhere.
Can regular expresion be used, CLASS=%Linux.* ?
Yes.
quoted from Steve Aiello
Can a host be defined to more than one class, i.e.
   1.2.3.4   serverName   # ssh CLASS:Linux CLASS:webServer
No.
quoted from Steve Aiello
If a host can have more than one class definition, what happens when you
get CLASS configuration parameter collision ?
That's why one host cannot belong to more than one class.


Regards,
Henrik