<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
<HTML><HEAD>
<META http-equiv=Content-Type content=text/html;charset=iso-8859-1>
<META content="MSHTML 6.00.6000.16825" name=GENERATOR></HEAD>
<BODY id=MailContainerBody
style="PADDING-RIGHT: 10px; PADDING-LEFT: 10px; PADDING-TOP: 15px"
bgColor=#ffffff leftMargin=0 topMargin=0 CanvasTabStop="true"
name="Compose message area">
<DIV><FONT face=Arial size=2>Hi Asif</FONT></DIV>
<DIV><FONT face=Arial size=2></FONT> </DIV>
<DIV><FONT face=Arial size=2></FONT> </DIV>
<DIV><FONT face=Arial size=2>There are a few questions need to be addressed for
non-home deployment.</FONT></DIV>
<DIV><FONT face=Arial size=2></FONT> </DIV>
<DIV><FONT face=Arial size=2>1. Do we want to have xymon
clients to query Sun's patch database file ?</FONT></DIV>
<DIV><FONT face=Arial size=2> The answer should be No for a
site have big xymon client installations.</FONT></DIV>
<DIV><FONT face=Arial size=2>2. the pca xymon client module should query
internal solaris patch database server(on xymon server).</FONT></DIV>
<DIV><FONT face=Arial size=2>3. the pca xymon server
side EXT module should in sync with Sun's patch database
server</FONT> <FONT face=Arial size=2>and download the zip files for
internal installation.</FONT></DIV>
<DIV><FONT face=Arial size=2>4. pca rely on wget and wget rely on other software
also, be prepared to deal with pca xymon module for solaris 2.6 and above that
doesn't come with wget.</FONT></DIV>
<DIV><FONT face=Arial size=2></FONT> </DIV>
<DIV><FONT face=Arial size=2></FONT> </DIV>
<DIV>
<DIV><FONT face=Arial size=2>I don't quite understand why you design pca work as
server side module</FONT></DIV>
<DIV><FONT face=Arial size=2></FONT> </DIV>
<DIV><FONT face=Arial size=2>For me, I did it as a client side module and create
another column (pca) for each xymon client.</FONT></DIV>
<DIV><FONT face=Arial size=2></FONT> </DIV>
<DIV><FONT face=Arial size=2>Here is an example of what it looks like so
far</FONT></DIV>
<DIV><FONT face=Arial size=2></FONT> </DIV>
<DIV><FONT face=Arial size=2><A
title="http://xymon.dlinkddns.com/hobbit-cgi/bb-hostsvc.sh?HOST=netinstall.test.net&SERVICE=pca
CTRL + Click to follow link"
href="http://xymon.dlinkddns.com/hobbit-cgi/bb-hostsvc.sh?HOST=netinstall.test.net&SERVICE=pca">http://xymon.dlinkddns.com/hobbit-cgi/bb-hostsvc.sh?HOST=netinstall.test.net&SERVICE=pca</A></FONT></DIV>
<DIV><FONT face=Arial size=2></FONT> </DIV></DIV>
<DIV><FONT face=Arial size=2>P.S. I interacted with pca author but failed to
convince him we (xymon community) can have a "-M" option to send out xymon
needed html format.</FONT></DIV>
<DIV><FONT face=Arial size=2></FONT> </DIV>
<DIV><FONT face=Arial size=2>tj</FONT></DIV>
<DIV><FONT face=Arial size=2></FONT> </DIV>
<DIV style="FONT: 10pt Tahoma">
<DIV><BR></DIV>
<DIV style="BACKGROUND: #f5f5f5">
<DIV style="font-color: black"><B>From:</B> <A
title="mailto:vadud3@gmail.com
CTRL + Click to follow link"
href="mailto:vadud3@gmail.com">Asif Iqbal</A> </DIV>
<DIV><B>Sent:</B> Thursday, May 14, 2009 1:41 PM</DIV>
<DIV><B>To:</B> <A title=hobbit@hswn.dk
href="mailto:hobbit@hswn.dk">hobbit@hswn.dk</A> </DIV>
<DIV><B>Subject:</B> [hobbit] Duration for one round of server side
module</DIV></DIV></DIV>
<DIV><BR></DIV><BR>I implemented a server side perl script using this <A
title="http://xymonton.trantor.org/doku.php/tutorials:ssmodule
CTRL + Click to follow link"
href="http://xymonton.trantor.org/doku.php/tutorials:ssmodule">http://xymonton.trantor.org/doku.php/tutorials:ssmodule</A>
as the template. <BR><BR>I like to run it only once daily, so I put status+1d
for the bb command. <BR><BR>But I need help to find out how long it takes for
the script to complete for my ~300 hosts. <BR><BR>Currently I have it setup just
like the setup in the above url, like the following.
<BR><BR>[pca]<BR> ENVFILE
/export/home/hobbit/server/etc/hobbitserver.cfg<BR>
NEEDS hobbitd<BR> CMD hobbitd_channel
--channel=client --log=$BBSERVERLOGS/pca.log $BBHOME<BR>/ext/pca.pl<BR><BR>And
it is taking tons of resources since it receives all the patch/pkg info from 300
servers through client channel <BR>and generate a patch report using the tool
pca (<A
href="http://www.par.univie.ac.at/solaris/pca/">http://www.par.univie.ac.at/solaris/pca/</A>)
for each host. It allows us<BR>to find out the patch status for all solaris
boxes<BR><BR>Here is an snippet of the top processes sorted by
RSS<BR><BR> PID USERNAME SIZE RSS STATE PRI
NICE TIME CPU
PROCESS/NLWP <BR> 8687
hobbit 2248M 581M run
39 0 0:02:31 1.1% hobbitd_channel/1<BR> 8648
hobbit 58M 56M run
39 0 0:07:42 2.5% hobbitd/1<BR> 10223
hobbit 21M 20M run
20 0 0:00:03 15% perl5.8.5/1<BR> 7115
devmon 11M 11M sleep
59 0 0:00:44 1.5% devmon/1<BR> 8689
hobbit 8816K 6968K sleep 59
0 0:07:52 2.7% pca.pl/1<BR><BR>If I can find out how long it takes
to run I can then add an INTERVAL accordingly. I do not need to <BR>process the
client data more than once a day<BR><BR clear=all><BR>-- <BR>Asif Iqbal<BR>PGP
Key: 0xE62693C5 KeyServer: <A href="http://pgp.mit.edu">pgp.mit.edu</A><BR>A:
Because it messes up the order in which people normally read text.<BR>Q: Why is
top-posting such a bad thing?<BR><BR><BR></BODY></HTML>