Hi Justin,
(I'm adding back others in cc as the Debian BTS doesn't Cc people by
default.)
Justin Pasher (2019-07-15):
> > From: Cyril Brulebois
> >
> > But I'd be very happy to have success reports from sysvinit users
> > before considering backporting this to buster.
>
> I use sysvinit. I've
- Original Message -
> From: Cyril Brulebois
> Date: Friday, July 12, 2019 06:45:08 PM CDT
> Subject: Re: Bug#911604: haveged start up fails due to apparmor
denying write access to /run/haveged.pid
> To: Axel Beckert , 911604 <911...@bugs.debian.org>
> CC: Gert , D
Control: tag -1 patch pending
Hi,
Axel Beckert (2018-10-22):
> haveged silently fails to start on one of my machines, seemingly due
> to apparmor. From /var/log/syslog after unsucessfully trying to start
> haveged:
>
> Oct 22 15:40:26 someone haveged: haveged starting up
> Oct 22 15:40:26
The fix below worked for me too. However, this means the error is still
present in the buster version of the haveged package. I think it's a
little more important to get this fixed, as the Buster release notes
explicitly suggest using haveged as a possible means of improving the
RNG entropy on
I have having the same issue with sysvinit-core
On Sat, 1 Dec 2018 23:56:10 +0100 Gert wrote:
> > What helped was adding the line
> > /run/haveged.pid w,
> > to /etc/apparmor.d/local/usr.sbin.haveged
>
> That works, thank you.
> FWIW, I did not have this problem when I used systemd as init.
>
What helped was adding the line
/run/haveged.pid w,
to /etc/apparmor.d/local/usr.sbin.haveged
That works, thank you.
FWIW, I did not have this problem when I used systemd as init.
I just switched to openrc-init, and then I did.
I don't know why that would make a difference.
Buster, i386,
Package: haveged
Version: 1.9.1-6
Severity: important
Tags: patch
Hi,
haveged silently fails to start on one of my machines, seemingly due
to apparmor. From /var/log/syslog after unsucessfully trying to start
haveged:
Oct 22 15:40:26 someone haveged: haveged starting up
Oct 22 15:40:26 someone
7 matches
Mail list logo
