From: Olaf Hering <olaf@aepfle.de>
To: Cal Peake <cp@absolutedigital.net>
Cc: Linus Torvalds <torvalds@osdl.org>,
Albert Cahalan <acahalan@gmail.com>,
linux-kernel <linux-kernel@vger.kernel.org>,
Andrew Morton <akpm@osdl.org>,
ebiederm@xmission.com
Subject: Re: sysctl
Date: Wed, 18 Oct 2006 21:12:49 +0200 [thread overview]
Message-ID: <20061018191249.GA19927@aepfle.de> (raw)
In-Reply-To: <Pine.LNX.4.64.0610181443170.7303@lancer.cnet.absolutedigital.net>
On Wed, Oct 18, Cal Peake wrote:
> On Wed, 18 Oct 2006, Linus Torvalds wrote:
>
> > There's apparently some library functions that has used it in the past,
> > and I've seen a few effects of that:
> >
> > warning: process `wish' used the removed sysctl system call
> >
> > but the users all had fallback positions, so I don't think anything
> > actually broke.
>
> Agreed, nothing seems to have broken by removing it but the warnings sure
> are ugly. Is there any reason to have them? If a program relies on sysctl
> and the call fails the program should properly handle the error. That
> should be all the warning that's needed (i.e. report the broken program
> and get it fixed).
You will not see the warning for your failing app anyway due to the max
tries == 5 limit. With SLES10 the boot scripts trigger it already.
next prev parent reply other threads:[~2006-10-18 19:13 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-10-18 18:23 sysctl Albert Cahalan
2006-10-18 18:27 ` sysctl David KOENIG
2006-10-18 18:31 ` sysctl Linus Torvalds
2006-10-18 18:52 ` sysctl Cal Peake
2006-10-18 19:12 ` Olaf Hering [this message]
2006-10-18 19:44 ` sysctl Andrew Morton
2006-10-18 21:06 ` sysctl Cal Peake
2006-10-19 4:41 ` [RFC] [PATCH] Improve the remove sysctl warnings Eric W. Biederman
2006-10-19 16:25 ` Cal Peake
2006-10-19 19:50 ` Alexey Dobriyan
2006-10-19 19:55 ` Cal Peake
2006-10-20 7:05 ` [CFT] Grep to find users of sys_sysctl Eric W. Biederman
2006-10-20 7:35 ` Andrew Morton
2006-10-20 12:54 ` Eric W. Biederman
2006-10-20 16:39 ` Andrew Morton
2006-10-21 10:23 ` Eric W. Biederman
2006-10-20 7:52 ` Russell King
2006-10-20 14:38 ` Eric W. Biederman
2006-10-20 15:18 ` Albert Cahalan
2006-10-21 10:53 ` Eric W. Biederman
2006-10-20 15:46 ` Bill Nottingham
2006-10-20 8:02 ` Jakub Jelinek
2006-10-20 13:41 ` Eric W. Biederman
2006-10-20 17:54 ` Marco Roeland
-- strict thread matches above, loose matches on Subject: below --
2001-04-01 10:48 sysctl Subba Rao
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20061018191249.GA19927@aepfle.de \
--to=olaf@aepfle.de \
--cc=acahalan@gmail.com \
--cc=akpm@osdl.org \
--cc=cp@absolutedigital.net \
--cc=ebiederm@xmission.com \
--cc=linux-kernel@vger.kernel.org \
--cc=torvalds@osdl.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox