Your message dated Sat, 29 Sep 2007 06:26:29 +0200 (CEST)
with message-id <[EMAIL PROTECTED]>
and subject line Bug#444465: Acknowledgement (S30procps.sh in /etc/rcS.d not
executed at boot time)
has caused the attached Bug report to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what I am
talking about this indicates a serious mail system misconfiguration
somewhere. Please contact me immediately.)
Debian bug tracking system administrator
(administrator, Debian Bugs database)
--- Begin Message ---
Package: procps
Version: 1:3.2.7-3
Severity: serious
Justification: Policy 9.3.1
Debian Policy Manual says:
9.3.1
"Also, if the script name ends in .sh, the script will be sourced in runlevel
S rather than being run in a forked subprocess, but will be explicitly run
by sh in all other runlevels."
/etc/rcS.d/S30procps.sh is not being executed properly by /etc/init.d/rcS
because of
this (or /etc/init.d/rc for that matter).
/etc/sysctl.conf settings, which may contain important parameters, are not
set properly during boottime because of this.
Spotted by: Marco Davids (SIDN) with help from #elders team, in particular
'koopal'.
-- System Information:
Debian Release: 4.0
APT prefers stable
APT policy: (500, 'stable')
Architecture: i386 (i686)
Shell: /bin/sh linked to /bin/bash
Kernel: Linux 2.6.18-5-686
Locale: LANG=C, LC_CTYPE=C (charmap=ANSI_X3.4-1968)
Versions of packages procps depends on:
ii libc6 2.3.6.ds1-13etch2 GNU C Library: Shared libraries
ii libncurses5 5.5-5 Shared libraries for terminal hand
ii lsb-base 3.1-23.2etch1 Linux Standard Base 3.1 init scrip
Versions of packages procps recommends:
ii psmisc 22.3-1 Utilities that use the proc filesy
-- no debconf information
--- End Message ---
--- Begin Message ---
This was a false alarm.
The parameters I set in /etc/sysctl.conf where:
net.ipv6.conf.eth0.accept_ra=0
net.ipv6.conf.eth0.autoconf=0
They where not executed.
Later I read somewhere:
"On Debian systems, kernel modules for some network interfaces (e.g. 10GE
cards) are not loaded before the init process executes the script that
runs the sysctl commands. In those cases, it is necessary to force the
module to be loaded earlier. The same goes for the IPv6 settings; the ipv6
module is usually not loaded until the network interfaces are brought up,
which is typically after the sysctl variables are set by the procps.sh
script."
This was probably the real cause of the problem.
Sorry for this.
--
Marco
--- End Message ---
