Hello,
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.
Regards,
Paul
On Saturday, May 31, 2003, at 07:04 PM, Paul Rolland wrote:
> Hello,
>
> 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 :)
------------------------------
Stewart Smith
[email protected]
Ph: +61 4 3884 4332
ICQ: 6734154
http://www.flamingspork.com/ http://www.linux.org.au
On Sat, 31 May 2003 11:04:20 +0200, 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.
If you have a line with 'update' or 'bdflush' in /etc/inittab,
remove it. (Its obsolete since mid-2.2 or so.)
Hello,
> On Sat, 31 May 2003 11:04:20 +0200, 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.
>
> If you have a line with 'update' or 'bdflush' in
> /etc/inittab, remove it. (Its obsolete since mid-2.2 or so.)
Nice guess ! I have
ud:once:/sbin/update
within inittab.
The puzzling part is that, if it obsolete since mid-2.2, why is it
present on a RedHat 8.0 install ?
However, this question is not important ;-)
Thanks for the info, I'm gonna clean this !
Regards,
Paul
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.
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
On Sunday 01 June 2003 21:31, Felipe Alfaro Solana wrote:
> "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.
calling syscall bdflush() triggers this warning.
this syscall is obsolete.
Things can now be done through /proc/sys/vm
- --
Regards Michael B?sch
http://www.8ung.at/tuxsoft
22:07:21 up 2:53, 3 users, load average: 1.00, 1.07, 1.06
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.1 (GNU/Linux)
iD8DBQE+2l1hoxoigfggmSgRApnXAJkBfQw8CBVaUmJRuCNGA/8oZOAPygCfYREJ
sHauLAtZZfbcbAC+P9OL3BE=
=zBAB
-----END PGP SIGNATURE-----