[OpenAFS] Modifying the output of vos commands to include server UUIDs

Steve Simmons scs@umich.edu
Wed, 14 Apr 2010 13:52:17 -0400

On Apr 14, 2010, at 11:23 AM, Jeffrey Altman wrote:

> On 4/14/2010 10:51 AM, Steve Simmons wrote:
>> On Apr 13, 2010, at 5:28 PM, Jeffrey Altman wrote:
>>>> I'm a long-time fan of having a switch that causes tools to dump =
their data in an easy-to-machine-parse format. That isn't always doable, =
but when it is, it's a big win.
>>> As Andrew pointed out in another reply in this thread, the -format
>>> switch is support to provide that but it fails to provide a =
>>> (value - data) pair per line.
>> Exactly my point. We currently snarf off all that data nightly via =
script that parses the output from vos e -format. It works but was a =
>> Note, tho, that some data doesn't adapt well to single-line output. =
For example,=20
>> just doesn't map well to single-line. We currently deal with this by =
creating four records, each will all the data from the rest of the =
output and the specifics of the four entries above.
>> Steve
> Anyone want a -xml option?

Parsing xml in ad-hoc shell scripts is hell. On the other hand, all our =
nightly data gathering scripts are in languages that have appropriate =
xml parsers available. So yes, it would be useful. Or to be more =
precise, it would *also* be useful. But comma-separated still has big =
wins for some things.