Hey Tony, I've seen this too. I don't know what the events.from was designed for. I've seen XenCenter using it for a "fast"-sync with the pool, and features some kind of logging (see id=0, class=message). I think you can safely skip all events with id=0 and accept the ts=0 as given :)
I handle the pool syncing a little bit different, which is slower, bit a bit more straight forward: 1. event.register(*) 2. foreach($obj_types as $type) $type.get_all() 3. while($running) event.next() Greetings Uli Stärk -----Ursprüngliche Nachricht----- Von: xen-api-boun...@lists.xen.org [mailto:xen-api-boun...@lists.xen.org] Im Auftrag von tony_caot...@163.com Gesendet: Mittwoch, 16. September 2015 04:39 An: xen-us...@lists.xen.org; xen-api@lists.xen.org Betreff: [Xen-API] value of timestamp from API event.from() is always '0' Hi all, My xenserver version is 6.2 When I fetch logs from API function event.from(), the value of each timestamp field is always '0.' . Instead of event.next(), it is fine. Could anyone give me some advices ? -- ----------- Cao Tong _______________________________________________ Xen-api mailing list Xen-api@lists.xen.org http://lists.xen.org/cgi-bin/mailman/listinfo/xen-api _______________________________________________ Xen-api mailing list Xen-api@lists.xen.org http://lists.xen.org/cgi-bin/mailman/listinfo/xen-api