[rrd-developers] Question: rrdtool pipe interface - restore support?

[Peter Stamfest]

I have implemented this. And yes, it might be useful. I might support it
in my java interface to rrd.

My implementation can be found in branch pipe-restore in my repo at
https://github.com/stamfest/rrdtool-1.x#

Note that I haven't rebased/merged the stuff into master. If I should do
this, just say so.

peter



Am 2014-02-16 10:00, schrieb Tobi Oetiker:
> I think it should be possible to get this to work since I am using the
> pull parser in rrdtool restore
>
> cheers
>
> Tobias Oetiker
> tobi at oetiker.ch <mailto:tobi at oetiker.ch>
> 062 775 9902
>
> On 16.02.2014, at 03:21, Stanislav Sinyagin <ssinyagin at yahoo.com
> <mailto:ssinyagin at yahoo.com>> wrote:
>
>> 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 <peter at stamfest.at <mailto:peter at stamfest.at>>
>> *To:* rrd-developers at lists.oetiker.ch
>> <mailto:rrd-developers at lists.oetiker.ch>
>> *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
>> rrd-developers at lists.oetiker.ch <mailto:rrd-developers at lists.oetiker.ch>
>> https://lists.oetiker.ch/cgi-bin/listinfo/rrd-developers
>>
>>
>> _______________________________________________
>> rrd-developers mailing list
>> rrd-developers at lists.oetiker.ch <mailto:rrd-developers at lists.oetiker.ch>
>> https://lists.oetiker.ch/cgi-bin/listinfo/rrd-developers
>
>
> _______________________________________________
> rrd-developers mailing list
> rrd-developers at lists.oetiker.ch
> https://lists.oetiker.ch/cgi-bin/listinfo/rrd-developers


-- 
---------------------------------------------------------------------
Dipl.-Ing. Peter Stamfest     UNIX, Networking & Computing Consultant
Tel: +43/699/10711205         Software Development - Internetservices
E-Mail: peter at stamfest.at     WWW: http://stamfest.at/

-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.oetiker.ch/pipermail/rrd-developers/attachments/20140225/079a4023/attachment-0001.htm