Re: Chnage in exit codes of #gluster volume heal command

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



> In addition, I would recommend considering using --xml and that
> picking out the field you want to look at with a quick xml parser, and
> then going with that directly. More stable than watching for a
> specific return code.

Parsing XML to get one bit of information doesn't seem like a great
idea.  If the script needs exact counts then sure, parse away, but if
all it needs to know is whether any are non-zero then what's wrong
with having that reflected in the exit code?  That's far easier for a
script to interpret, and there's plenty of precedent for using exit
codes this way.
_______________________________________________
Gluster-devel mailing list
Gluster-devel@xxxxxxxxxxx
http://supercolony.gluster.org/mailman/listinfo/gluster-devel




[Index of Archives]     [Gluster Users]     [Ceph Users]     [Linux ARM Kernel]     [Linux ARM]     [Linux Omap]     [Fedora ARM]     [IETF Annouce]     [Security]     [Bugtraq]     [Linux]     [Linux OMAP]     [Linux MIPS]     [eCos]     [Asterisk Internet PBX]     [Linux API]

  Powered by Linux