On Thu, 2006-03-02 at 14:00 -0500, Jean-Sebastien Morisset wrote:
Can we use an AND in the monitor line? Something like:
monitor -r 70 -o dskPath -o dskErrorMsg dskTable dskErrorFlag != 0
dskUsed = 0
Not directly.
The Event MIB is designed to monitor a single value - not
arbitrary
On Fri, Mar 03, 2006 at 10:37:37AM +, Dave Shield wrote:
On Thu, 2006-03-02 at 14:00 -0500, Jean-Sebastien Morisset wrote:
Can we use an AND in the monitor line? Something like:
monitor -r 70 -o dskPath -o dskErrorMsg dskTable dskErrorFlag != 0
dskUsed = 0
Not directly.
The Event
On Thu, Mar 02, 2006 at 01:08:49PM +, Dave Shield wrote:
On Wed, 2006-03-01 at 15:09 -0500, Jean-Sebastien Morisset wrote:
On Wed, Mar 01, 2006 at 09:27:30AM +, Dave Shield wrote:
Can you try walking the UCD-SNMP-MIB:dskTable
Ah, of course, I didn't notice that dskTable in the error
On Thu, 2006-03-02 at 09:38 -0500, Jean-Sebastien Morisset wrote:
I was able to reproduce the problem. I copied a few gigs on the
filesystem and then removed it. Right after, I ran an snmpwalk. It stuck
for second half way through, and then gave me the following:
dskTotal.2 = INTEGER:
On Thu, Mar 02, 2006 at 02:53:04PM +, Dave Shield wrote:
On Thu, 2006-03-02 at 09:38 -0500, Jean-Sebastien Morisset wrote:
I was able to reproduce the problem. I copied a few gigs on the
filesystem and then removed it. Right after, I ran an snmpwalk. It stuck
for second half way through,
On Thu, Mar 02, 2006 at 02:53:04PM +, Dave Shield wrote:
On Thu, 2006-03-02 at 09:38 -0500, Jean-Sebastien Morisset wrote:
I was able to reproduce the problem. I copied a few gigs on the
filesystem and then removed it. Right after, I ran an snmpwalk. It stuck
for second half way through,
