Re: [hobbit] problem with CLASS definition

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

I did some poking around, and as far as I can tell, the problem is due 
to hobbitclient.cfg overriding the CONFIGCLASS variable.
Here are some snippets from runclient.sh:

--class=*)
               CONFIGCLASS="`echo $1 | sed -e 's/--class=//' | tr 
'[A-Z]' '[a-z]'`"

export MACHINE MACHINEDOTS BBOSTYPE BBOSSCRIPT HOBBITCLIENTHOME CONFIGCLASS

hobbitclient.cfg contains this:
./hobbitclient.cfg:CONFIGCLASS="$BBOSTYPE"         # Default 
configuration class for logfiles

hobbitclient.sh uses the CONFIGCLASS variable when sending the client 
message:
./bin/hobbitclient.sh:echo "client $MACHINE.$BBOSTYPE $CONFIGCLASS"  >>  
$MSGTMPFILE

Heres the actual client message header Im sending (not that CONFIGCLASS  
is being set to "linux" instead of the specified class:
client host-app-23.linux linux

-Charles


Charles Jones wrote:
> Anyone have any thoughts on this? I'm currently dead in the water 
> without this working as it should.  I tried emailing Henrik as well 
> but I'm sure he is too busy to reply.
>
> -Charles
>
> Charles Jones wrote:
> > I have a host whose client was started via: "./runclient.sh 
> > --class=APP_PRIMARY start"
> >
> > In the hobbit servers hobbit-clients.cfg, I have something similar to:
> >
> > CLASS=APP_PRIMARY
> >    PROC "someproc"
> >    PROC "/some/other/proc"
> > ....
> > DEFAULT
> >    PROC sshd
> >
> > The problem is that only the default proc "sshd" is being checked on 
> > the host.  The expected behavior is that the CLASS would be used and 
> > other other procs checked instead. I know this has nothing to do with 
> > the DEFAULT setting, as using HOST=hostname works fine. I just cant 
> > get it to check the procs by CLASS.  Is there any way to debug this?  
> > Shouldn't the CLASS show up in the "info" section?  Do I need to put 
> > the class name in quotes on the command line?
>
> To unsubscribe from the hobbit list, send an e-mail to
> hobbit-unsubscribe (at) hswn.dk