[Nagiosplug-devel] [ nagiosplug-Bugs-1523748 ] check_disc uninitialized variable

SourceForge.net noreply at sourceforge.net
Mon Jul 17 17:46:33 CEST 2006

Bugs item #1523748, was opened at 2006-07-17 11:37
Message generated for change (Comment added) made by vandenburgd
You can respond by visiting: 

Please note that this message will contain a full copy of the comment thread,
including the initial issue submission, for this request,
not just the latest update.
Category: None
Group: None
>Status: Open
Resolution: None
Priority: 5
Submitted By: Dick van den Burg (vandenburgd)
Assigned to: Ton Voon (tonvoon)
Summary: check_disc uninitialized variable

Initial Comment:
the new se->w_idfp and se->c_idfp in version 1.4.3 are
not initialized resulting in the following error (on
HP-UX 11.23)

check_disk -c 5% -w 10%  -p /dev/vg00/lvol1
INPUT ERROR: C_IDFP (0.000000) should be less than
and both should be between zero and 100 percent,
inclusive for /dev/vg00/lvol1
check_disk: Could not parse arguments
Usage: check_disk -w limit -c limit [-p path | -x
device] [-t timeout][-m] [-e] [-W limit] [-K limit]
[-v] [-q]
The following patch corrects this

*** check_disk.c        Mon Jul 17 11:32:26 2006
--- check_disk.c.good   Mon Jul 17 11:32:03 2006
*** 462,467 ****
--- 462,469 ----
        se->c_df = c_df;
        se->w_dfp = w_dfp;
        se->c_dfp = c_dfp;
+       se->w_idfp = w_idfp;
+       se->c_idfp = c_idfp;
        se->found = 0;
        se->found_len = 0;
        *pathtail = se;


>Comment By: Dick van den Burg (vandenburgd)
Date: 2006-07-17 17:46

Logged In: YES 

As the changes in CURRENT deleted every reference to w_idfp
and c_idfp the error also disappears. Unfortunately the
consistency check also dispappeared.



Comment By: Ton Voon (tonvoon)
Date: 2006-07-17 12:27

Logged In: YES 


Can you try the snapshot at http://nagiosplug.sourceforge.net/snapshot. There 
have been fixes to check_disk recently. Please update if there is still a problem.

I've marked the call in pending so it will autoclose in 7 days.



You can respond by visiting: 

More information about the Devel mailing list