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 f
In message <[EMAIL PROTECTED]>, Skye Poier Nott writes
:
>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
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-liblo
