Conference noted::sns

1027.0. "sensor_lop arg list... what is the 1 for???" by CIMBAD::SHUMWAY () Tue May 06 1997 10:11

Hello I am running an agent on Unix and am trying to congigure the looping 
process sensor.  Up till now we have been taking the defaults, and that has 
been working well, but recently we added a process that uses a mailbox that 
has pushed the threshold over the limit, so we need to reconfigure PSW.

The first thing I wanted to do was to set the -t flag from 25 to 40, but it 
didn't seem to help, so I tried to set it to 5 just to make sure my changes
actually changing something.  nothing happened, so I moved on to the -c flag 
and again no matter what I set it to the default 90 was the actual result.

When I look at the process I see this...

..... /usr/opt/psw/psw_sensor_lop 1 -x/dev/null -c30

When I envoke it myself from the command line I see this

..... /usr/opt/psw/psw_sensor_lop -x/dev/null -c30

I notice that the agent adds in a 1 in the arg list.  When I run it myself 
from the command line the -c arg works.  I have also noticed in the notes 
in this group there are 1's in others listings.

Could someone please clear me on this, or is everyone just using the defaults???

Thank You,
Keith Shumway


here is my psw_agent.conf 

.....
#Looping interval in seconds
120
#Obsolete delay in hours
24
#
#Supported sensors
CPU,MEM,DSK psw_sensor_syswd permanent  free   nodata -x/dev/null
LOP         psw_sensor_lop   cron       filter nodata '-x/dev/null -c30'
DNF         psw_sensor_dnf   cron       filter flow   -x/dev/null
PRO         psw_sensor_pro   cron       filter flow   -x/dev/null
PRS         psw_sensor_prs   cron       filter flow   -x/dev/null
ETH         psw_sensor_eth   cron       filter nodata -x/dev/null
......