Re: [Networker] mminfo -- when did binary change?

Probably easier to change your script to query the variables you would like to 
see. This will prevent any future output changes from messing up your script as 
well.
Change your mminfo to something like this:
mminfo -s $server -r 'volume(10),written(10),read(10),mounts(10),capacity(10)' 
-q 'savetime>=blahblah...

This will give you the output as expected, then use perl's split() for instance 
to get the appropriate variables assigned.


Jorgen Lie


-----Original Message-----
From: George Sinclair [mailto:George.Sinclair AT NOAA DOT GOV]
Sent: Monday, February 03, 2003 4:14 PM
To: NETWORKER AT LISTMAIL.TEMPLE DOT EDU
Subject: [Networker] mminfo -- when did binary change?


Hi,

Does anyone know when the mminfo command was changed to include the
volume expiration date?

I had a Perl script that runs the mminfo command and parses the results.
I always ran this on an older Sun client. One day I decided to copy the
script to a Linux box. I figured Perl is portable so no big deal. Oddly,
though, I start seeing strange results on the Linux box from the output.
I finally figured out that the mminfo command generates one more field
(the volume exp. date) when run from the Linux machine and hence the
culprit.

Here's the first three lines ouf output from the command on the older
Sun client:

mminfo -s orion -vm -q
'pool=FUL,level=full,savetime>=01/20/03,savetime<=01/30/03'
   volume                  written  (%)    read mounts capacity
volid      next type
   FUL372                    46 GB full    0 KB    23     70 GB
3733098497  176 dlt7000
   FUL373                    75 GB full    0 KB    43     70 GB
3733152769  306 dlt7000

Now, here's what I see on a newer Linux client when running the same
command:

mminfo -s orion -vm -q
'pool=FUL,level=full,savetime>=01/20/03,savetime<=01/30/03'
   volume                  written  (%) expires      read mounts
capacity volid      next type
   FUL372                    46 GB full 01/20/04     0 KB    23     70
GB 3733098497  176 dlt7000
   FUL373                    75 GB full 01/25/04     0 KB    43     70
GB 3733152769  306 dlt7000

Obviously, we're dealing with two different OS here, but here's the
binary info:

Sun: -rwxr-xr-x   1 root     staff     846844 Aug 10  2000
/usr/sbin/mminfo*

Linux: -rwxr-xr-x    1 root     root       636304 Oct 16  2001
/usr/sbin/mminfo*

I guess the sun client's legato client needs to be upgraded? Maybe
easier than modifying the script to check the header line to know
whether it's picking up an extra field or not?

Thanks.

George
George.Sinclair AT noaa DOT gov

--
Note: To sign off this list, send a "signoff networker" command via email
to listserv AT listmail.temple DOT edu or visit the list's Web site at
http://listmail.temple.edu/archives/networker.html where you can
also view and post messages to the list.
=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=

--
Note: To sign off this list, send a "signoff networker" command via email
to listserv AT listmail.temple DOT edu or visit the list's Web site at
http://listmail.temple.edu/archives/networker.html where you can
also view and post messages to the list.
=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=