From mboxrd@z Thu Jan  1 00:00:00 1970
From: Miklos Vajna <vmiklos@frugalware.org>
Date: Thu, 19 Jan 2012 20:31:19 +0000
Subject: Re: systemd38 + rsyslog
Message-Id: <20120119203119.GK27966@genesis.frugalware.org>
MIME-Version: 1
Content-Type: multipart/mixed; boundary="Gv4AD2GulCTyUAWX"
List-Id: <linux-hotplug.vger.kernel.org>
References: <alpine.LNX.2.01.1201191501560.4280@waverley.dhcp.wfu.edu>
In-Reply-To: <alpine.LNX.2.01.1201191501560.4280@waverley.dhcp.wfu.edu>
To: linux-hotplug@vger.kernel.org


--Gv4AD2GulCTyUAWX
Content-Type: text/plain; charset=utf-8
Content-Disposition: inline
Content-Transfer-Encoding: quoted-printable

On Thu, Jan 19, 2012 at 03:26:18PM -0500, Allin Cottrell <cottrell@wfu.edu>=
 wrote:
> I made the symlink, and the boot-up error disappeared. But it=20
> had a nasty side-effect: now systemctl poweroff and systemctl=20
> reboot stopped working. These commands put the machine into a=20
> zombie-like state (blank screen with a blinking cursor at the=20
> top left); it was necessary to stop the machine with the power=20
> button. It took me a while to figure out what was responsible=20
> for this behavior, but when I deleted the syslog.service=20
> symlink, poweroff and reboot started working again -- though=20
> of course the boot-error message is back.

Sound like the issue commit ead51eb4ed55981f290e40a871ffbca6480c4cd3
already solved.

--Gv4AD2GulCTyUAWX
Content-Type: application/pgp-signature

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.11 (GNU/Linux)

iEYEARECAAYFAk8YfZcACgkQe81tAgORUJZqQwCgliwRCbPmQcQZJg5NQHcp6Pu6
eV4An2UykwDx565Eby6MFgQzyg7GpUu3
=2Sve
-----END PGP SIGNATURE-----

--Gv4AD2GulCTyUAWX--