I assume this is for logging daemon metadata/error conditions and not actual traffic?
If this is for request/response logging, consider implementing a bridge daemon that reads from the SHM like varnishlog or varnishncsa does, and which then sends the output via liblogging. This will provide the fastest possible performance without bogging down Varnish, and makes it such that it can be updated or modified entirely independent of varnish itself. --Michael On Tue, Oct 7, 2008 at 2:46 PM, Skye Poier Nott <[EMAIL PROTECTED]> wrote: > Hello again, > > I'm currently working on adding liblogging (reliable syslog over BEEP) > support to varnishncsa. > http://www.liblogging.org/ > > Is this something that the project would be interested in adding to > trunk when it's done? I presume it would need to be wrapped in a > configure --with-liblogging option (default off) > > Thanks, > Skye > > _______________________________________________ > varnish-misc mailing list > [email protected] > http://projects.linpro.no/mailman/listinfo/varnish-misc > > _______________________________________________ varnish-misc mailing list [email protected] http://projects.linpro.no/mailman/listinfo/varnish-misc
