From: Felipe Alfaro Solana <felipe_alfaro@linuxmail.org>
To: Stewart Smith <stewartsmith@mac.com>
Cc: Paul Rolland <rol@witbe.net>, LKML <linux-kernel@vger.kernel.org>,
rol@as2917.net
Subject: Re: warning: process 'update' used the obsolete bdflush...
Date: 01 Jun 2003 21:31:40 +0200 [thread overview]
Message-ID: <1054495899.943.2.camel@teapot.felipe-alfaro.com> (raw)
In-Reply-To: <1B8F41EC-934B-11D7-B416-00039346F142@mac.com>
On Sat, 2003-05-31 at 11:34, Stewart Smith wrote:
> On Saturday, May 31, 2003, at 07:04 PM, Paul Rolland wrote:
> > When switching from 2.4.20 to 2.5.x (x being recent), I have this
> > message...
> >
> > What does this mean ?
> > 1 - I have no process named update running,
> > 2 - I can't find anything name update in /etc/rc.d/* recursively.
>
> from fs/buffer.c:
> /*
> * There are no bdflush tunables left. But distributions are
> * still running obsolete flush daemons, so we terminate them here.
> *
> * Use of bdflush() is deprecated and will be removed in a future
> kernel.
> * The `pdflush' kernel threads fully replace bdflush daemons and this
> call.
> */
>
> I'd upgrade whatever package update comes from. I can't seem to find
> that binary around on some of my systems, what distribution and version
> are you running? Maybe it's time to upgrade.
>
> Someone else might know specifics :)
"update" is not a program, but a kernel daemon that was superseded by
pdflush in 2.5 kernels. I just can't remember right know what caused
that warning, but it's similar to the SO_BSDCOMPAT warning that is
triggered when running bind.
next prev parent reply other threads:[~2003-06-01 19:18 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-05-31 9:04 Paul Rolland
2003-05-31 9:34 ` Stewart Smith
2003-06-01 19:31 ` Felipe Alfaro Solana [this message]
2003-06-01 20:09 ` Michael Buesch
2003-05-31 10:53 mikpe
2003-05-31 11:51 ` Paul Rolland
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=1054495899.943.2.camel@teapot.felipe-alfaro.com \
--to=felipe_alfaro@linuxmail.org \
--cc=linux-kernel@vger.kernel.org \
--cc=rol@as2917.net \
--cc=rol@witbe.net \
--cc=stewartsmith@mac.com \
/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
all inboxes | Powered by JetHome®