Re: [Peerguardian-devel] pgld: logging

[jre-phoenix <jre...@us...>]

Oh, I forgot: I will add logging to dbus support to pglcmd, too. If I
find out ho to do it. Currently I´m working on log to syslog support
for pglcmd.

On Thu, Oct 29, 2009 at 11:07 PM, jre-phoenix
<jre...@us...> wrote:
>> To begin with, will the date always be in this format? I think that I had
>> this problem with moblock. Sometimes the date format was different on
>> different computers and as a result parsing the log was a problem.
>
> I think Cade can give a clear answer here.
>
>> Moreover, I strongly believe that we should use a double pipe instead of
>> just one. I don't think it will be that messy and it will prevent some
>> strange descriptions containing pipes from causing any problems.
>
> Currently "everything between first pipe and end of line" is the
> description. But if you think this can cause problems, then we can
> easily change that, no problem.
>
>> As for the entries refering to an error, please make sure they have the word
>> *error* somewhere in them so that I can mark them as such.
>>
>> To sum up, from what I understand the format will be:
>> *mmm dd hh:mm:ss hostname pgld: General_Entry_Here*
>>
>> or
>>
>> *mmm dd hh:mm:ss hostname pgld: IN/OUT/FWD: ...*
>
> Again for Cade, best give the concrete line of code.
>
>> Am I right? If this is always the case, parsing the log would not be too
>> difficult. What about dbus entries however? How are they formated?
>
> But what I really want to say: pgld now has three output options,
> where ALL output goes:
> - log to logfile
> - log to syslog
> - log to dbus
> From all that I know, dbus is THE interface to exchange things between
> e.g. a daemon and a GUI. So I think the GUI should only listen to
> dbus, but not parse the logfiles. Unfortunately I don´t know dbus
> really yet. But I will work on understanding it, and I suggest you do
> so, too.
> Even more unfortunately dbus output is broken currently with our
> recent push, but we will definitely reenable it.
> Maybe you don´t even have to parse dbus log messages for "Error", if
> it is possible to just get the importance of the log message (in the
> code we already have LOG_INFO, LOG_WARNING and LOG_ERR)
>
> BTW, one point for dbus is, that it solves the problem with too big
> logfiles (mobloquer was nearly dead if you had a 16MB logfile).
>