Change the scheduling favor of running processes to tame heavy jobs or boost urgent tasks. 25.04.2026 | reading time: 2 min Renice lets him change the scheduling priority of running processes so he can make a CPU-hungry job yield or give a latency-sensitive task more CPU favor; it acts immediately on the selected processes. Why adjust priorities On a multiuser server a long compilation or backup can make interactive shells sluggish; renice lets him push that workload down and restore snappy responsiveness without killing jobs. Quick example in action Start a simple background job, inspect its nice value, renice it and verify the change: ```bash sleep 300 & # prints PID, for example 12345 ps -o pid,ni,comm -p 12345 # PID NI COMMAND # 12345 0 sleep renice -n 10 -p 12345 # 12345: old priority 0, new priority 10 ps -o pid,ni,comm -p 12345 # PID NI COMMAND # 12345 10 sleep ``` Options and permissions The main flags are -n to set the increment or absolute change, -p for PID, -g for process group and -u for user; the valid nice range is -20 to 19 and only root can assign negative (higher) priorities. When renice is not enough For persistent or cgroup-level control he should use systemd slices, cgroups or cpulimit; renice is great for quick fixes but not for long-term resource policies or I/O priority, where ionice and systemd settings are better suited. Try it and grow Experiment on disposable processes to see immediate effects, then explore scripting and systemd integration to automate priority handling; for structured learning consider CompTIA Linux+ or LPIC-1 exam preparation and intensive courses at bitsandbytes.academy to deepen hands-on skills. Join Bits & Bytes Academy First class LINUX exam preparation. processes utilities troubleshooting
