On Oct 7, 6:18 am, Vinay Sajip wrote:
> Thanks for the detailed report. I tried posting a response a couple of times,
> but Google appears to have swallowed it ... trying again. Sorry if it results
> in
> multiple responses.
Hmm, I too seem to be experiencing this problem...
> The SysLogHandler
On Oct 7, 6:18 am, Vinay Sajip wrote:
> Thanks for the detailed report. I tried posting a response a couple of times,
> but Google appears to have swallowed it ... trying again. Sorry if it results
> in
> multiple responses.
Hmm, I too seem to be experiencing this problem...
> The SysLogHandler
On Oct 7, 6:18 am, Vinay Sajip wrote:
> Thanks for the detailed report. I tried posting a response a couple of times,
> but Google appears to have swallowed it ... trying again. Sorry if it results
> in
> multiple responses.
I tried to respond yesterday, but I also noticed this probelm.
> The S
On Oct 6, 6:56 pm, "Dustin C. Hatch" wrote:
>
> My question, therefore, is where does this problem lie? Is it a bug in
> Metalog that it doesn't properly parse the message, or is it a bug in
> SysLogHandler that it doesn't properly format it? I guess it could
> also be that if one wants to use t
I have a daemon that uses the built-in SysLogHandler logging handler
class to log messages to the host's syslog. Unfortunately, I am having
trouble getting it to work with Metalog[1]. At first, I thought the
problem was Metalog's fault because everything works as expected with
syslog-ng. Upon furt
