Hello,
It seems that procps version = 3.2.8-8 doesn't fix the problem. I run a
Debian Squeeze and at boot time, I get :
Setting kernel variables ...
error: net.ipv6.bindv6only is an unknown key
error: net.ipv6.conf.eth0.autoconf is an unknown key
failed.
Theses keys are in files under the
On Tue, Jun 29, 2010 at 10:56:09AM +0200, Jérémie Rodriguez wrote:
It seems that procps version = 3.2.8-8 doesn't fix the problem. I run a
Debian Squeeze and at boot time, I get :
Did you read the README file in /usr/share/doc/procps? It explains some
about this.
Anyone has the problem anymore
Hello,
My fault, I didn't read the README file (RTFM is always for others :) ).
I tried one of the solutions explained in this file : putting ipv6 in
/etc/modules. After a reboot, the kernel system variables concerning
IPv6 are set as expected.
For information, I use the Debian Xen kernel which
[Craig Small]
That's the thing I was asking for :) But the problem is (AFAIK) that
with LSB dependencies one can only specify depends and not kind of
reverse depends.
The init.d headers can have reverse dependencies too. Those are
X-Start-Before and X-Stop-After. Check
On Tue, 2009-08-25 at 15:04 +1000, Craig Small wrote:
On Fri, Aug 14, 2009 at 12:04:55AM +0200, Christoph Anton Mitterer wrote:
The issue that sysctl MUST be loaded BEFORE network interfaces are
brought up (for security reasons) is this secured by the LSB
init script headers?
You're
On Fri, Aug 14, 2009 at 12:04:55AM +0200, Christoph Anton Mitterer wrote:
The issue that sysctl MUST be loaded BEFORE network interfaces are
brought up (for security reasons) is this secured by the LSB
init script headers?
You're saying it should be done before the interfaces are brought
Hi.
Apart from the question, whether anything new has happened here?
The issue that sysctl MUST be loaded BEFORE network interfaces are
brought up (for security reasons) is this secured by the LSB init
script headers?
I mean now that insserv and concurrent booting moves to be the
also sprach Didier Raboud [EMAIL PROTECTED] [2008.12.05.1342 +0100]:
As ipv6 is a release goal, my guess is that a solution has to be found.
Maybe the easiest solution is simply to load the ipv6 module early
on, unconditionally?
--
.''`. martin f. krafft [EMAIL PROTECTED] Related
On Fri, Dec 05, 2008 at 01:42:50PM +0100, Didier Raboud wrote:
As ipv6 is a release goal, my guess is that a solution has to be found.
Then, why not getting opininons by consulting -devel about
It will break things, not might, it will. The easiest examples being
anything that uses the
On Thu, Dec 04, 2008 at 02:26:54PM +0100, martin f krafft wrote:
The ipv6 module on Debian is loaded only by the networking code, so
either sysctl.conf should run after that, or the ipv6 module needs
to be loaded before somehow.
There is no sensible fix for this. The problem is that any time
also sprach Craig Small [EMAIL PROTECTED] [2008.12.05.1211 +0100]:
There is no sensible fix for this. The problem is that any time is the
wrong time for the init script to run, for someone.
Do you have specific examples that would break if procps ran at S40?
--
.''`. martin f. krafft
On Fri, Dec 05, 2008 at 12:29:43PM +0100, martin f krafft wrote:
also sprach Craig Small [EMAIL PROTECTED] [2008.12.05.1211 +0100]:
There is no sensible fix for this. The problem is that any time is the
wrong time for the init script to run, for someone.
Do you have specific examples that
Le vendredi 5 décembre 2008 12:35:44 Craig Small, vous avez écrit :
On Fri, Dec 05, 2008 at 12:29:43PM +0100, martin f krafft wrote:
also sprach Craig Small [EMAIL PROTECTED] [2008.12.05.1211 +0100]:
There is no sensible fix for this. The problem is that any time is the
wrong time for
Package: procps
Version: 1:3.2.7-9
Severity: serious
Tags: ipv6
File: /etc/sysctl.conf
Setting kernel variables (/etc/sysctl.conf)...error:
net.ipv6.conf.default.autoconf is an unknown key
error: net.ipv6.conf.default.accept_ra is an unknown key
error: net.ipv6.conf.default.accept_ra_defrtr is an
14 matches
Mail list logo
