From dunne@accuweather.com Wed Jun 24 08:15:06 2026 From: dunne@accuweather.com To: xymon@xymon.com Subject: NFS and shared clientlaunch.cfg files Date: Wed, 15 Aug 2007 17:07:51 -0400 Message-ID: <200708151707.AA93192976@ntms1.accuweather.com> MIME-Version: 1.0 Content-Type: multipart/mixed; boundary="===============1232931525343449383==" --===============1232931525343449383== Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: quoted-printable Greetings fellow Hobbit-ers, I was recently tasked with monitoring 100+ solaris systems. Feeling undaunted= I reached into=20 my trusty IT toolbox and pulled out one of my favorite tools, Hobbit. What I = encountered is=20 as followed.=20 The systems utilize NFS mounted directories. I installed the client files int= o /usr/local/ hobbit/client and voila! they were available to all of my systems. The issue = that I encountered=20 was that I wished to run different external scripts per client, but with a "s= hared" clientlaunch=20 file I could not see how to do this. (This is where I cringe as I suspect tha= t my solution is=20 rather naive) What I would up doing is modifying the runclient.sh file as ref= lected below: ~/client hobbit$ diff runclient.sh runclient.ren=20 79c79 < $0 --hostname=3D"$MACHINEDOTS" stop --- > $0 stop 83c83 < $HOBBITCLIENTHOME/bin/hobbitlaunch --config=3D$HOBBITCLIENTHOME/etc/ clientlaunch.cfg --log=3D$HOBBITCLIENTHOME/logs/clientlaunch.log --pidfile=3D $HOBBITCLIENTHOME/logs/clientlaunch.$MACHINEDOTS.pid --- > $HOBBITCLIENTHOME/bin/hobbitlaunch --config=3D$HOBBITCLIENTHOME/etc/ $MACHINEDOTS.clientlaunch.cfg --log=3D$HOBBITCLIENTHOME/logs/ $MACHINEDOTS.clientlaunch.log --pidfile=3D$HOBBITCLIENTHOME/logs/clientlaunch. $MACHINEDOTS.pid 102c102 < $0 --hostname=3D"$MACHINEDOTS" stop --- > $0 stop 107c107 < $0 --hostname=3D"$MACHINEDOTS" --os=3D"$BBOSTYPE" start --- > $0 start My questions are as followed.=20 Has anyone encountered this specific issue before, and if so how did you addr= ess it? Does my, admittedly inelegant, solution pose any issues in relation to long t= erm use?=20 I searched the list and was unable to find anything specific to my issue.=20 Thanks in advance for reading this missive. Best regards, Mike --===============1232931525343449383==-- From jonescr@cisco.com Wed Jun 24 08:15:06 2026 From: jonescr@cisco.com To: xymon@xymon.com Subject: [hobbit] NFS and shared clientlaunch.cfg files Date: Wed, 15 Aug 2007 15:20:58 -0700 Message-ID: <46C37C4A.7080309@cisco.com> In-Reply-To: <200708151707.AA93192976@ntms1.accuweather.com> MIME-Version: 1.0 Content-Type: multipart/mixed; boundary="===============6689436959333371773==" --===============6689436959333371773== Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: quoted-printable I encountered this exact problem, with monitoring a few hundred servers=20 that had a common NFS filesystem. For the most part, Hobbit handles this=20 gracefully as it uses unique names for logfiles and such. I ran into=20 problems though when I wanted an extra script to run, but just on=20 certain hosts. I ended up just having the ext script check the hostname=20 and exit gracefully if it was not the host it should run on: HOSTNAME=3D`/bin/hostname` if ! echo $HOSTNAME | egrep -q 'app-28|web-12|web-13|db-10' ; then exit 0 fi What I would really like to see (and I posted this on the list before),=20 is a server-side configuration of what scripts or even commands to run=20 on the remote hosts. I doubt this will be implemented though, because=20 too many people view it as a security risk. What I proposed was a=20 config file with a format something like: