On 07/23/2011 01:32 AM, Christian Hergert wrote:
Can syslog() potentially block? If so, that might be an issue of
concern. I don't think it is, at least officially stated, that
syslog() is re-entrant safe (which may be of concern with regard to
how signals are handled).
well, this depends the
On 07/23/2011 12:34 AM, Marty Jack wrote:
The primary reason you wouldn't use syslog to log user messages is that it
opens the possibility for an unprivileged user process to maliciously consume
the root partition. Logging to the equivalent of ~/.Xsession-errors is the
right way to go becau
On Fri, Jul 22, 2011 at 2:34 PM, Marty Jack wrote:
>
>
> On 07/22/2011 04:01 PM, Tiago Vignatti wrote:
>> Hi all,
>>
>> I wanted to use an already existent library for logging; the first that came
>> to my mind was one with syslog interface. I like because there is a lot of
>> implementations arou
On 07/22/2011 04:01 PM, Tiago Vignatti wrote:
> Hi all,
>
> I wanted to use an already existent library for logging; the first that came
> to my mind was one with syslog interface. I like because there is a lot of
> implementations around, it's simple and kinda flexible. For instance, I can
> g
Hi all,
I wanted to use an already existent library for logging; the first that came
to my mind was one with syslog interface. I like because there is a lot of
implementations around, it's simple and kinda flexible. For instance, I can get
the whole system log together with the Wayland one if I wa
