Menu

#1 bdf -l on HPUX long volume name

open
nobody
None
5
2001-06-27
2001-06-27
Anonymous
No

In netsaint_statd.pl for HP_UX.

"sub" disk does not correctly parse the bdf output
correctly when a volume name is pretty long.

Please See:

<BEGIN>
*****************
ips1@/opt/ips/nobeleps >bdf -l
Filesystem kbytes used avail %used
Mounted on
/dev/vg00/lvol3 122880 52411 66105 44% /
/dev/vg00/lvol1 95701 42226 43904 49% /stand
/dev/vg00/lvol8 819200 663887 146031 82% /var
/dev/vg00/lvol7 819200 549471 252917 68% /usr
/dev/vg00/lvol6 512000 144977 344605 30% /tmp
/dev/vg00/lvol5 819200 490233 308449 61% /opt
/dev/vg00/lvol10 1282048 941133 319670
75% /opt/oracle
/dev/vg00/lvol9 1048576 811842 222077
79% /opt/ips
/dev/vg00/lvol4 20480 1242 18093 6% /home
/dev/vgora1/shared_lvol
21995520 17413867 4295383 80% /db1
/dev/vgora2/shared_lvol2
22007808 12009256 9842328 55% /db2
/dev/vgora3/shared_lvol3
22007808 14977072 6920888 68% /db3
ips1@/opt/ips/nobeleps >
*****************
<END>

Notice how the kbytes,used,avai, %used are on the next
line.

I would Image that we would look at the length of the
volume name and modify the perl

if (/^([\w\/\:\.]*)\s*\d*\s*\d*\s*(\d*)\s*(\d*)\%\s*
([\w\/]*)/)

to look for a CR,LF ?

to correctly parse and return the Disk Info.

Discussion


Log in to post a comment.

MongoDB Logo MongoDB