Most if not all Linux distribution use either "kill -15 -1" or
"killall5 -15" and later with -9 when going down or going to
single user mode to make sure all processes are gone. This will
kill kswapd. Especially when going multi usre -> single user ->
multi user this is problematic.
If killall5 is used, it could try to work around this by not killing
processes called "kswapd", but how can the ksapd process be
uniquely identified to prevent users from starting up processes
called "kswapd" that will never get killed (and thus prevent
unmounting filesystems when going down etc) ?
I'd prefer it if kswapd was made unkillable again.
Mike.
-- Indifference will certainly be the downfall of mankind, but who cares?- 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/