Le 16/02/12, Tobias Frilling a écrit :
> On 02/16/2012 07:13 PM, ianux wrote:
> > What's the difference between this syslog-ng.service file and the
> > one from syslog-ng ?
> > Beside the Alias line, you only duplicate the Sockets line which
> > already exists.
>
> Yeah, the duplication was an
On 02/16/2012 07:13 PM, ianux wrote:
> What's the difference between this syslog-ng.service file and the one
> from syslog-ng ?
> Beside the Alias line, you only duplicate the Sockets line which already
> exists.
Yeah, the duplication was an accident (might have happened out of frustration).
My pr
Le 15/02/12, Tobias Frilling a écrit :
> If somebody still is interested in this, here is my follow-up:
>
> After some digging (it is amazing how little information exist for
> this, not even a man page for anything journal related) I came to the
> conclusion that journal/socket is not meant fo
Oh, and syslog should probably not read from /proc/kmsg
(see
http://lists.freedesktop.org/archives/systemd-devel/2012-January/004310.html)
If somebody still is interested in this, here is my follow-up:
After some digging (it is amazing how little information exist for this, not
even a man page for anything journal related) I came to the conclusion that
journal/socket is not meant for a logging daemon to read from. Instead
journal/sys
To give a few more examples: With syslog-ng reading journal/socket:
- No logging for cron daemon (fcron)
- No logging at all in log/auth.log
- Only some few kernel messages in log/everything.log
- No logging with logger(1)
The list goes on ...
On 02/15/2012 02:30 PM, Giorgio Lando wrote:
> On Wed 15/02/12, 13:28, Christian Hesse wrote:
>>> - Why are the logs read from /run/systemd/journal/socket incomplete and
>>> how do I fix this?
>
>> /dev/log gives the messages only once. If two processes read from there it's
>> just random which g
On Wed 15/02/12, 13:28, Christian Hesse wrote:
> > - Why are the logs read from /run/systemd/journal/socket incomplete and
> > how do I fix this?
> /dev/log gives the messages only once. If two processes read from there it's
> just random which gets which messages. Probably that is why your logs
Tobias Frilling on Wed, 15 Feb 2012 12:35:56
+0100:
> On 02/09/2012 03:29 PM, Dave Reisner wrote:
> > - With the journal enabled (and it is enabled by default), you no longer
> > need to run a syslog daemon (i.e. syslog-ng or rsyslog). The journal,
> > by default, writes to /run/systemd/journa
On 02/09/2012 03:29 PM, Dave Reisner wrote:
> - With the journal enabled (and it is enabled by default), you no longer
> need to run a syslog daemon (i.e. syslog-ng or rsyslog). The journal,
> by default, writes to /run/systemd/journal (meaning logs will poof on
> reboot). If you want to keep
10 matches
Mail list logo
