Your message dated Mon, 7 Apr 2008 05:27:09 +0530
with message-id <[EMAIL PROTECTED]>
and subject line Re: Bug#471308: procps: sysctl.conf values are not activated
during boot time
has caused the Debian Bug report #471308,
regarding procps: sysctl.conf values are not activated during boot time
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 this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact [EMAIL PROTECTED]
immediately.)
--
471308: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=471308
Debian Bug Tracking System
Contact [EMAIL PROTECTED] with problems
--- Begin Message ---
Package: procps
Version: 1:3.2.7-6
Severity: important
On system boot, I've noticed that the sysctl.conf kernel tunable
settings are not activated. If I manually run sysctl -p, then it takes
those settings.
Ritesh
-- System Information:
Debian Release: lenny/sid
APT prefers testing
APT policy: (990, 'testing'), (600, 'unstable'), (150, 'experimental')
Architecture: i386 (i686)
Kernel: Linux 2.6.24-1-686 (SMP w/2 CPU cores; PREEMPT)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/bash
Versions of packages procps depends on:
ii libc6 2.7-6 GNU C Library: Shared libraries
ii libncurses5 5.6+20080203-1 Shared libraries for terminal hand
ii lsb-base 3.1-24 Linux Standard Base 3.1 init scrip
Versions of packages procps recommends:
ii psmisc 22.6-1 Utilities that use the proc filesy
-- no debconf information
--- End Message ---
--- Begin Message ---
On Monday 07 April 2008, Craig Small wrote:
> I would be surprised if this is actually the case as there would be
> many, many more bugreports like this. However what often can happen is
> that the settings do not take because the values apply to things that
> are not there or they are overwritten.
>
> This usually happens with settings to network devices, for example.
> Can you give me an specific example of where this is happening?
I think the bugreport could be invalid.
I just tried to look closer. Currently I have two settings
# Auto Reboot in 30 seconds on Kernel Panic
kernel.panic = 30
# This wakes the disk up less frequenty for background VM activity
vm.dirty_writeback_centisecs = 1500
I noticed that kernel.panic gets set correctly whereas dirty_writeback
doesn't. I confirm that because I've put a similar echo statement in rc.local
but still it is showing 499. Probably something is changing it dynamically.
We can close this bugreport.
Ritesh
--
Ritesh Raj Sarraf
RESEARCHUT - http://www.researchut.com
"Necessity is the mother of invention."
signature.asc
Description: This is a digitally signed message part.
--- End Message ---
