> >>This is after running inode hog. Fine to this point. (However in clean
> >>2.2.2-pre2 the number is bigger, that's fine too as I have some free memory)
> >
> >It's not fine according to me. Could you try to kill your update daemon
> >and see how much you can grow such number with many of your hog test?
>
> Umm?
>
> "Could you try to kill 'init' and see how long your machine survives
> without running out of processes due to processes getting stuck in
> zombie state?"
>
> If you kill the update deamon, your screwed. Don't do it. If you do
> it, whatever happens is your own fault, and you only have yourself to
> blame.
Linus, please, don't do this.
It is sometimes usefull to have update suspended. If you have a
notebook, and your drives are spinned down, it is bad idea to run
update.
Up till now, everything was ok, because kernel accessed disk anyway
when it needed. Up till now killing update was safe. I depend on this
behaviour and would like if it stayed safe.
This is not the same as killing init. (Killing init did not use to
work before.)
Pavel
-- I'm really pavel@atrey.karlin.mff.cuni.cz. Pavel Look at http://atrey.karlin.mff.cuni.cz/~pavel/ ;-).- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.rutgers.edu Please read the FAQ at http://www.tux.org/lkml/