17e9ffb46b1476ef97f532d6b81f2615dc
[4]: update address lifetimes on RENEW/RENEW6 (#1032809)
https://github.com/vaijab/fedora-dhcp/commit/543c1a58140be99fcd528a505ccdee7f4aaec535
[5]: git://anonscm.debian.org/pkg-dhcp/isc-dhcp.git
>From 60a6b8282bd145a6caa2e0451d5f777d01642e45 Mon Sep 17 00:00:00 200
I'm hitting the same problem. I can reproduce it on systemd 215 and
sysv 2.88.
On Jessie with systemd 215, there is a consistent 30 second pause
between each line of output, and this regular output seems to be due
to systemd actually writing lots of output, seemingly via the kernel
kprintf functi
I believe this error is rather an artifact of the ntpd/ntpd.c patch in
ntp_4.2.8p4+dfsg-3's debian/patches/ntpd-linux-caps-runtime.patch. That
patch checks Linux capabilities by calling cap_from_text, but it does
not include the CAP_IPC_LOCK capability, which is needed to make mmap(2)
work; mma
I reworked JH Chatenet's suggestion and submitted it upstream:
https://github.com/dex4er/fakechroot/pull/37>. I'll try to reach
the maintainer through various channels, as the last fakechroot
repository log entry was in Jan 2014.
best wishes,
Sven Ulland
Package: yum
Version: 3.4.3-3
Severity: normal
Dear Maintainer,
After a Yum-based bootstrap, the RPM database remains empty, and thus
causes problems for rpm and Yum itself:
* RPM thinks that zero packages are installed. It will happily
install packages that are already installed by Yum.
* Yu
Package: keepalived
Version: 1:1.2.9-1
Jessie should be updated to keepalived v1.2.10 or newer to avoid
IPv6 realserver problems.
keepalived versions before commit 2c89ddb [1], included in v1.2.10,
fail to add/remove IPv6 realservers to the ipvs table if the
keepalived daemon does the ip_vs modu
Having an option to require a trust path would be good. It can be off
by default to avoid compatibility issues and creeping security lax.
As it stands, there is no convenient way to require signature
verification with debootstrap itself, so I'm currently working around
it with an additional scrip
Pacemaker is built without corosync quorum support.
Could it be you didn't enable the pacemaker service in the corosync
configuration? I ran into the same problem, and did the following to
make it work:
cat > /etc/corosync/service.d/pcmk << EOF
service {
name: pacemaker
ver: 1
}
EOF
sven
On 10/18/2012 11:32 PM, Tormod Volden wrote:
I understand your opinion, and it is sad to "hide" this cool effect.
But we as a distribution have many different users and we sometimes
have to play safe with our defaults at the expense of coolness.
My preference would still be the initial suggesti
Tags: patch
Attached simple patch to move the offending hacks to -data-extra.
>From da4dda5a65af8759f485c00f0d7caef30a4d3edf Mon Sep 17 00:00:00 2001
From: =?UTF-8?q?"Sven=20Ulland=1B[C"?=
Date: Fri, 31 Aug 2012 16:37:12 +0200
Subject: [PATCH] Move distort,ripples,slidescreen to -data-extra.
Th
Package: xscreensaver-data
Version: 5.15-3
Severity: normal
Some hacks reveal the system's desktop, which is a potential security
issue. The xscreensaver package depends on xscreensaver-data, which
includes three hacks of this type: distort, ripples and slidescreen.
I'd suggest moving these from
Package: xscreensaver-data
Version: 5.15-3
Severity: minor
Some hacks reveal the system's desktop, which is a potential security
issue. The xscreensaver package depends on xscreensaver-data, which
includes three hacks of this type: distort, ripples and slidescreen.
I'd suggest moving these from x
Seconded. Also reported in [1]. The status of this issue is also the
same in Wheezy's linux-image-3.0.0-1-amd64 and experimental's
linux-image-3.1.0-rc7-amd64_3.1.0~rc7-1~experimental.1_amd64.deb
I haven't been able to figure out if enabling CONFIG_CRASH_DUMP adds
any overhead at all. Are there o
13 matches
Mail list logo
