On Sat, 2010-08-07 at 19:40 +0200, Hannes Frederic Sowa wrote: > On Sat, Aug 7, 2010 at 7:26 PM, seth vidal <skvidal@xxxxxxxxxxxxxxxxx> wrote: > > That's cool. there are now history plugin hooks that might help you - > > they're in yum 3.2.28. > > Cool - I will have a look at them. I'll be blunt, though - you'll need some kind of client-authenticated system to push this data to a common server. In order to keep any client on the system from being able to fill your server with garbage data. A couple of options: 1. reverse it and have a client connect in and fetch the data at regular intervals 2. look at something like func to do the communication. > I thought about letting PluginYumExit cancel the yum operation, that's alright. > If some other Exception happens it should be catched and logged but not > kill of the other yum-plugins. It depends how you trust the yum-plugins. > > Currently I am not too much into the yum-codebase. But if I see it correctly > the plugin-exceptions kill of yum before running verifyTransaction. Either > protect the codepath there that verifyTransaction is always called or the > function call could be pushed up. > I agree with as far as exceptions go - we can improve those and if you see cases, I think that's a fair thing to do. But at some points a plugin can just go horribly wrong and call sys.exit() or a library can abort and then you're just hosed. -sv _______________________________________________ Yum mailing list Yum@xxxxxxxxxxxxxxxxx http://lists.baseurl.org/mailman/listinfo/yum
