Hi Daniel, 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 :) 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? >
