|
On 17 Feb 2000, Doug Bagley wrote:
> I don't really want to discuss XML too much on this list, it could get
> into an off-topic religious discussion :-)
:-)
> I'm just wondering about the format of the ipvs information in /proc,
> which is basically the same human readable format printed by "ipvsadm".
It used to be the same in 0.8.3 (which we're running) whereas it's not
under the latest versions...
> I'd like to see a more machine readable format, but I don't think it
> would be appropriate to put XML in /proc.
Agreed :-)
It strikes me that rather than having:
type serviceIP:port mechanism
-> realip:port tunnel weight active inactive
-> realip:port tunnel weight active inactive
-> realip:port tunnel weight active inactive
-> realip:port tunnel weight active inactive
If the table was more like:
type serviceIP:port mechanism realip:port tunnel weight active inactive
Then this would make shell/awk/perl/etc scripts that do things with this
table easier to cobble together.
> That seems like a far reaching precedent to me. On the other hand, if
> the ipvsadm command wished to have a option to represent that
> information in XML, I can see how that could be useful.
This reminds me I should really finish tweaking the prog I wrote to allow
pretty printing of the ipvsadm table, and put it somewhere else for others
to play with if they like - it allows you to specify a template file for
formatting the output of of ipvsadm, making displaying the stuff as XML,
HTML, plain text, etc simpler/quicker. (It's got a few hardcoded settings
at the mo which I want to ditch first :-)
Michael
--
National & Local Web Cache Support R: G117
Manchester Computing T: 0161 275 7195
University of Manchester F: 0161 275 6040
Manchester UK M13 9PL M: Michael.Sparks@xxxxxxxxxxxxxxx
----------------------------------------------------------------------
LinuxVirtualServer.org mailing list - lvs-users@xxxxxxxxxxxxxxxxxxxxxx
To unsubscribe, e-mail: lvs-users-unsubscribe@xxxxxxxxxxxxxxxxxxxxxx
For additional commands, e-mail: lvs-users-help@xxxxxxxxxxxxxxxxxxxxxx
|
