Well if we turn them off (systemctl disable/stop) then all logs go to
the journal (this is the behaviour we want anyway, i just checked this
on the M0 target if dlog is not running and the magic
/home/developer/.platforminfologgingmode file exists all logs go to the
journal ). So it could be a good thing to remove dlog services and force
all logs to go to the systemd journal.
On 04/01/2014 02:02 PM, "Łukasz" Stelmach wrote:
It was <2014-04-01 wto 13:02>, when Roman Kubiak wrote:
On 04/01/2014 10:29 AM, ?ukasz Stelmach wrote:
It was <2014-03-31 pon 16:25>, when Lukasz Wojciechowski wrote:
Is there a choosen way of logging events from native or system
services in Tizen?
journald
I wasn't able to find anything about it on wiki pages or on mailing lists.
There are already some used solutions:
* configuring systemd to gather logs in journal
This is the prefered way. The easiest way to log a message is
printf(SD_NOTICE "Hello world!");
For more details please read
http://0pointer.de/blog/projects/journal-submit.html
* there is syslog
No there isn't. It is journald that opens and listens to /dev/log to
emulate syslog for legacy service.
* some services use dlog.
dlog is definitely deprecated.
Does this mean we could remove dlog from the image.
Yes, provided that you make sure nothing uses it. I don't know the
current state but I suspect there may still be some services using
dlog. You need to check it for yourself.
--
--------------
Roman Kubiak
--------------
_______________________________________________
Dev mailing list
[email protected]
https://lists.tizen.org/listinfo/dev
