On Wed, Jan 21, 2015 at 12:12:14PM +0000, Daniel P. Berrange wrote: [..snip..] > So I'm intending to create a standalone virtlogd daemon to address this > problem. Similarly to virtlockd, it will be able to re-exec itelf so > that upgrades can be done with no interruption to logging, and libvirtd > will talk to it over a simple RPC protocol.
This is a great idea! The naming might cause confusion though, having virtlogd and virtlockd within the same source tree it's easy to get them mixed up since both sound almost the same. Maybe virtloggingd although slightly longer avoids that confusion? Cheers, -- Guido -- libvir-list mailing list libvir-list@redhat.com https://www.redhat.com/mailman/listinfo/libvir-list
