From mboxrd@z Thu Jan  1 00:00:00 1970
Return-path: <ptxdist-bounces@pengutronix.de>
Received: from mail.eckelmann.de ([217.19.183.94])
	by metis.ext.pengutronix.de with esmtp (Exim 4.72)
	(envelope-from <prvs=1602fa2de9=G.Schenk@eckelmann.de>)
	id 1TEHHy-0003St-Cd
	for ptxdist@pengutronix.de; Wed, 19 Sep 2012 12:13:51 +0200
Received: from mail.eckelmann.de (localhost.localdomain [127.0.0.1])
	by localhost (Email Security Appliance) with SMTP id
	E02E1178AC33_599ADDB
	for <ptxdist@pengutronix.de>; Wed, 19 Sep 2012 10:13:49 +0000 (GMT)
Received: from dag.eckelmann.group (ex-dag01.eckelmann.group [192.168.13.8])
	(using TLSv1 with cipher AES128-SHA (128/128 bits))
	(Client CN "*.eckelmann.group",
	Issuer "Eckelmann Root CA" (not verified))
	by mail.eckelmann.de (Sophos Email Appliance) with ESMTPS id
	D4513178AC2E_599ADDF
	for <ptxdist@pengutronix.de>; Wed, 19 Sep 2012 10:13:49 +0000 (GMT)
From: "Schenk, Gavin" <G.Schenk@eckelmann.de>
Date: Wed, 19 Sep 2012 10:13:48 +0000
Message-ID: <D415CD2EC4182C4EAB90A76B7D9F16DCA96FEE71@EX-DAG02.eckelmann.group>
Content-Language: de-DE
MIME-Version: 1.0
Subject: [ptxdist] rsyslog does not work with systemd 189
Reply-To: ptxdist@pengutronix.de
List-Id: PTXdist Development Mailing List <ptxdist.pengutronix.de>
List-Unsubscribe: <http://metis.pengutronix.de/cgi-bin/mailman/options/ptxdist>, 
	<mailto:ptxdist-request@pengutronix.de?subject=unsubscribe>
List-Archive: <http://metis.pengutronix.de/pipermail/ptxdist>
List-Post: <mailto:ptxdist@pengutronix.de>
List-Help: <mailto:ptxdist-request@pengutronix.de?subject=help>
List-Subscribe: <http://metis.pengutronix.de/cgi-bin/mailman/listinfo/ptxdist>, 
	<mailto:ptxdist-request@pengutronix.de?subject=subscribe>
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Sender: ptxdist-bounces@pengutronix.de
Errors-To: ptxdist-bounces@pengutronix.de
To: "ptxdist@pengutronix.de" <ptxdist@pengutronix.de>

Hi,

rsyslog does not work with systemd 189. One cause is the systemd unitfile delivered with rsyslog.
It looks like:

<SNIP>
[Unit]
Description=System Logging Service

[Service]
ExecStartPre=/bin/systemctl stop systemd-kmsg-syslogd.service
ExecStart=@sbindir@/rsyslogd -n -c6
Sockets=syslog.socket
StandardOutput=null
</SNIP>

But in newer systemd environments it should look like:
[Unit]
Description=System Logging Service
Requires=syslog.socket

[Service]
ExecStart=/usr/sbin/syslog-ng -n
StandardOutput=null

[Install]
Alias=syslog.service
WantedBy=multi-user.target

The systemd-kmsg-syslogd.service does not exist anymore and this leads to infinite errors during bootup. I had a look to newer versions of rsyslog, but even in rsyslog 7.1.3 the rsyslog.service.in looks the same old way.

I am not sure what is the best way to fix this? Meantime I use a local patch in my project.

Regards
Gavin
Eckelmann Aktiengesellschaft
Vorstand: Dr.-Ing. Gerd Eckelmann (Vorsitzender)
Dr.-Ing. Peter Cordes, Dr.-Ing. Frank-Thomas Mellert
Vorsitzender des Aufsichtsrats: Hubertus G. Krossa
Sitz der Gesellschaft: Wiesbaden Amtsgericht Wiesbaden HRB 12636

-- 
ptxdist mailing list
ptxdist@pengutronix.de