Am 07.11.2015 um 12:59 schrieb Zbigniew Jędrzejewski-Szmek:
On Fri, Nov 06, 2015 at 06:20:39PM +0100, Reindl Harald wrote:


Am 06.11.2015 um 18:15 schrieb Subhendu Ghosh:

On Nov 6, 2015 9:52 AM, "Reindl Harald" <h.rei...@thelounge.net
<mailto:h.rei...@thelounge.net>> wrote:

who is responsible that nothing is forwarded to the traditional syslog?
systemd or rsyslog?


Journald is probably hold the log socket and not forwarding to syslog

it does not need to Forward the old way hence "ForwardToSyslog=no"
and instead "$ModLoad imjournal" which is nothing new but don't work
at Rawhide currecntly while it dooes on F20/F21/F22/f23

http://www.rsyslog.com/doc/v8-stable/configuration/modules/imjournal.html

to say it in other words: i did not ask for "probably", just pointed
out that Rawhide is currently broken, that probably systemd or
probably rsyslog is broken in the one or other direction is clear

I looks like a problem on the rsyslog side, from what you describe.
A permission issue seems the most likely

permission to what?

since rsyslog with "imjournal" reads data from journald than it sounds more like an systemd regression if it's a permission issue (no SELinux is part of the game here)



Attachment: signature.asc
Description: OpenPGP digital signature

-- 
devel mailing list
devel@lists.fedoraproject.org
https://admin.fedoraproject.org/mailman/listinfo/devel
Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct

Reply via email to