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 servers
Related Q&A from Kenneth Milberg
Learn which makes more sense for your enterprise: building your own cloud-based diagnostic tooling or purchasing an existing product. Expert Ken ... Continue Reading
Learn about Helm Charts and how Kubernetes supports a microservices architecture. Expert Ken Milberg discusses what you need to know before delving ... Continue Reading
As blockchain matures, an ecosystem of tools continues to sprout up around it. Learn how these offerings, including the Hyperledger Fabric Client SDK... 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.