It was <2013-10-22 wto 07:38>, when juho son wrote:
> On 10/22/2013 01:58 PM, Ylinen, Mikko wrote:
>>
>> On Tue, Oct 22, 2013 at 2:54 AM, Rusty Lynch <[email protected]
>> <mailto:[email protected]>> wrote:
>>
>>> I'm not sure what changed, although an ivi kernel change is likely
>>> the issue, but for some reason we do not automatically load the
>>> logger kernel module.  I can get past this by modprobing the logger
>>> module.
>>
>>
>> https://review.tizen.org/gerrit/#/c/10927/
>>
>> How about we enable libdlog output to journal?
>
> Journal logging system have big problems to apply our system directly.
> Journald have been having HIGH cpu usage.(of course having power
> consumption problem)
>
> Many developers have to change their log and learn about journal.
> of course we could change only libdlog output to journal,
> It's just alternative code. Finally we should change all log to journal.
> so not to easy.

Compiling libdlog with systemd journal as a backend is in my opinion
enough for most developers.

-- 
Łukasz Stelmach
Samsung R&D Institute Poland
Samsung Electronics

Attachment: pgpR97nWlem3A.pgp
Description: PGP signature

_______________________________________________
Dev mailing list
[email protected]
https://lists.tizen.org/listinfo/dev

Reply via email to