Hi Krishnan,
On Tue, 2009-12-08 at 14:26 +0530, krishnan parthasarathi - Sun
Microsystems - Bangalore India wrote:
> I had time-slider in mind when I thought about the python bindings. I am
> also aware of time-slider forking a subprocess to run zfs commands, to
> gather information, which is precisely my motivation :)
Yep, I agree - I think time-slider would benefit from a better python
library (although even the current approach I think could be optimised)
Could you get in touch with Niall on zfs-auto-snapshot at opensolaris.org
who's the current maintainer to discuss?
cheers,
tim
> I will first look into the effort already gone into this as pointed in
> this thread.
>
> Thanks,
> Krishnan
>
> On 12/ 8/09 03:43 AM, Daniel Carosone wrote:
> > I don't grok python at all, and digging through the time-slider code
> has proven it :) It invokes command lines and pretends to present
> python objects, forking a lot and grabbing lots of repeated output for
> just one item.
> >
> > If you can write new code that uses libzfs in the backend, and
> presents the same (or very similar) api to the consumers like
> time-slider, that would seem to slot in the best.
> >
> > Note also that the time-slider stuff is all being rewritten, perhaps
> that has covered some of this ground already, or at least has altered
> some of that api?
> >
>
> _______________________________________________
> zfs-code mailing list
> zfs-code at opensolaris.org
> http://mail.opensolaris.org/mailman/listinfo/zfs-code
