I go to 'rm -rf foo,' realize that the directory foo is HUGE (50+GB), hit ctr-z, and try to background it in an
effort to move on with my life.
Under 2.4, the process would suspend immediately, background immediately, and the interactive response was perfect (IMHO).
Under 2.6, I hit ctr-z, and nothing happens for up to 30 seconds.
Eventually the process suspends, and then I can background it, but it's totally unnerving. It makes me feel like I'm using Windows.
Is this a real change in 2.6, or am I doing something wrong? Did the scheduler change between 2.4 and 2.6?
nohupto run your jobs in the background, and you will be in good shape; it's really a better practice than job suspension anyhow.
For more information:
Read Mark Hinkle's answer to this question, in which he explains how to change the process priority.
Dig deeper on Linux news and updates
Related Q&A from Kenneth Milberg
Unix-to-Linux migration expert Ken Milberg describes how virtualization, support, clustering and more fit into the migration of an IT infrastructure ...continue reading
A reader new to Linux wonders about which distribution is recommended for installing Nagios and what Nahant and Tikanga mean.continue reading
Documentation for Red Hat Enterprise Linux 5 covering checking system performance, tuning, kernel configuration and extending the file system exists ...continue reading
Have a question for an expert?
Please add a title for your question
Get answers from a TechTarget expert on whatever's puzzling you.