Displaying 5 results from an estimated 5 matches for "level_name".
2020 Jun 02
2
problem with logger: syslog vs. file
...t;lwp, call_identifier_str,
> msg->file, msg->line, msg->function, msg->message);
> term_strip(buf, buf, size);
> break;
>
> case LOGTYPE_FILE:
> snprintf(buf, size, "[%s] %s[%d]%s %s: %s",
> msg->date, msg->level_name, msg->lwp,
> call_identifier_str, msg->file, msg->message);
> term_strip(buf, buf, size);
> break;
>
>
> so basically, it is hardcoded that logging to syslog adds extra
> msg->line and msg->function.
>
> why would anybody do that ?
>...
2019 Nov 16
2
problem with logger
Hello,
I am logging directly into file and also to syslog.
Here is snippet from my /etc/asterisk/logger.conf:
messages => notice,warning,error,verbose
syslog.local0 => notice,warning,error,verbose
But the logs look different:
VERBOSE[7609][C-00000013] pbx.c:
NOTICE[3042] chan_sip.c: Peer '1111' is now UNREACHABLE!
vs.
VERBOSE[7609][C-00000013]: pbx.c:2925 in
2020 Jun 02
0
problem with logger: syslog vs. file
...levels[msg->level], msg->lwp, call_identifier_str,
msg->file, msg->line, msg->function, msg->message);
term_strip(buf, buf, size);
break;
case LOGTYPE_FILE:
snprintf(buf, size, "[%s] %s[%d]%s %s: %s",
msg->date, msg->level_name, msg->lwp,
call_identifier_str, msg->file, msg->message);
term_strip(buf, buf, size);
break;
so basically, it is hardcoded that logging to syslog adds extra
msg->line and msg->function.
why would anybody do that ?
This seems to me like a very unfortunate decisio...
2020 Jun 03
0
problem with logger: syslog vs. file
...;> msg->file, msg->line, msg->function, msg->message);
>> term_strip(buf, buf, size);
>> break;
>>
>> case LOGTYPE_FILE:
>> snprintf(buf, size, "[%s] %s[%d]%s %s: %s",
>> msg->date, msg->level_name, msg->lwp,
>> call_identifier_str, msg->file, msg->message);
>> term_strip(buf, buf, size);
>> break;
>>
>>
>> so basically, it is hardcoded that logging to syslog adds extra
>> msg->line and msg->function.
>>
>&g...
2020 Jun 03
2
problem with logger: syslog vs. file
...ne, msg->function, msg->message);
> >> term_strip(buf, buf, size);
> >> break;
> >>
> >> case LOGTYPE_FILE:
> >> snprintf(buf, size, "[%s] %s[%d]%s %s: %s",
> >> msg->date, msg->level_name, msg->lwp,
> >> call_identifier_str, msg->file, msg->message);
> >> term_strip(buf, buf, size);
> >> break;
> >>
> >>
> >> so basically, it is hardcoded that logging to syslog adds extra
> >> msg->line an...