I don't think it does. Why isn't a usual file good enough? You can store it in
tmpfs if the i/o speed is the concern. But usually rrdtool is
slower than disk i/o anyway.
What I
typically do, is execute rrdtool dump from an SSH command, so that its
remote stdout is the ssh's local stdout, and save the XML to a local
temporary file. Next the local rrdtool restore would slurp that file.
If you need the XML to tweak some RRD parameter, you can use RRD::Tweak Perl
module instead.
________________________________
From: Peter Stamfest <[email protected]>
To: [email protected]
Sent: Friday, February 14, 2014 9:39 PM
Subject: [rrd-developers] Question: rrdtool pipe interface - restore support?
Hi,
Does the rrdtool pipe interface somehow support an in-stream xml restore
command?
"dump" is (mostly) working as expected, although one has to look for
the "OK" response line to find out where the xml ends, but this is not a
problem. "restore" however has the problem that it does not take input
over the pipe interface. Using "-" as XML input seems to *partly* work,
but fails with a parser error. Using /dev/stdin works when using the
pipe interface on the command line, but can't work when using the pipe
over a TCP connection....
Any ideas?
I admit that I am using a rather old version: 1.4.7...
peter
_______________________________________________
rrd-developers mailing list
[email protected]
https://lists.oetiker.ch/cgi-bin/listinfo/rrd-developers
_______________________________________________
rrd-developers mailing list
[email protected]
https://lists.oetiker.ch/cgi-bin/listinfo/rrd-developers
