yes, if it was started by systemd (ie: NOTIFY_SOCKET - https://git.enlightenment.org/core/efl.git/tree/src/lib/eina/eina_log.c#n1538) then it will send to journal.
If you want to selectively send to journal or reformat just some message, see http://www.gustavobarbieri.com.br/2012/10/27/eina_log-customizations.html then you can check the domain and log it to stderr as you wish, while forwarding all or the remaining domains to syslog/systemd/file. On Sat, Oct 29, 2016 at 3:42 PM, Davide Andreoli <d...@gurumeditation.it> wrote: > 2016-10-29 17:02 GMT+02:00 thomasg <tho...@gstaedtner.net>: > >> On Sat, Oct 29, 2016 at 4:41 PM, Felipe Magno de Almeida < >> felipe.m.alme...@gmail.com> wrote: >> >> > On Sat, Oct 29, 2016 at 3:23 AM, Carsten Haitzler <ras...@rasterman.com> >> > wrote: >> > > On Sat, 29 Oct 2016 01:50:21 -0200 Gustavo Sverzut Barbieri >> > > <barbi...@gmail.com> said: >> > >> > [snip] >> > >> > >> agreed, that's why it's nice to know if it was done in a thread or >> not. >> > >> >> > >> as for long lines, we already have separate vars that disable a big >> > >> part of it... maybe offer an EINA_LOG_SHORTLINE=1 that disables them >> > >> all? >> > > >> > > that makes sense. making thread info optional but the rest all there by >> > default >> > > makes no sense to me. having a "short line" that maybe just reports >> > filename >> > > +line number would be useful (that's enough to track it down in most >> > cases). >> > > remove the full path from the file too- just the last file after the >> > last / if >> > > there are /'s. :) >> > > >> > > and maybe a minimal which is just "ERR: xxx" where xxx is the log >> string >> > > content and no file/line/process etc. >> > > >> > > but thread info imho belongs together with pid and other such info >> > anyway.:) >> > >> > Considering that reproducing can be very difficult sometimes, I rather >> > have the maximum information possible and deal with "pollution" later. >> > > are you aware of the existance of: > eina_log_print_cb_set(...) > > you can customize the eina log output as you like in your app :) > > > >> > >> > > -- >> > > ------------- Codito, ergo sum - "I code, therefore I am" >> -------------- >> > > The Rasterman (Carsten Haitzler) ras...@rasterman.com >> > >> > >> > Regards, >> > -- >> > Felipe Magno de Almeida >> >> >> Maybe I should explain here I'm coming from: I'm actually still using some >> command line tools written in EFL (I wrote or started them before the >> merge, when EFL was still a reasonable choice for that), and one of my >> libraries uses eina_log. >> In this case it is, albeit rare, not unlikely, that a user will see log >> messages (certainly for errors). >> I realize that this is a non-issue for graphical apps started in a >> graphical session. >> >> I suppose in an ideal world, the basic log messages would appear on the >> command line, and all the details would be logged to journald, but we're >> not there yet :) >> ------------------------------------------------------------ >> ------------------ >> The Command Line: Reinvented for Modern Developers >> Did the resurgence of CLI tooling catch you by surprise? >> Reconnect with the command line and become more productive. >> Learn the new .NET and ASP.NET CLI. Get your free copy! >> http://sdm.link/telerik >> _______________________________________________ >> enlightenment-devel mailing list >> enlightenment-devel@lists.sourceforge.net >> https://lists.sourceforge.net/lists/listinfo/enlightenment-devel >> > ------------------------------------------------------------------------------ > The Command Line: Reinvented for Modern Developers > Did the resurgence of CLI tooling catch you by surprise? > Reconnect with the command line and become more productive. > Learn the new .NET and ASP.NET CLI. Get your free copy! > http://sdm.link/telerik > _______________________________________________ > enlightenment-devel mailing list > enlightenment-devel@lists.sourceforge.net > https://lists.sourceforge.net/lists/listinfo/enlightenment-devel -- Gustavo Sverzut Barbieri -------------------------------------- Mobile: +55 (16) 99354-9890 ------------------------------------------------------------------------------ The Command Line: Reinvented for Modern Developers Did the resurgence of CLI tooling catch you by surprise? Reconnect with the command line and become more productive. Learn the new .NET and ASP.NET CLI. Get your free copy! http://sdm.link/telerik _______________________________________________ enlightenment-devel mailing list enlightenment-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/enlightenment-devel