An ordinary user starts a process at nice 0.
They run nice -n -5 worker to move toward higher priority, without special resource limits.
Which result normally occurs?
Moving to a lower nice value is a higher-priority change and is restricted. It normally requires CAP_SYS_NICE or an allowed RLIMIT_NICE.
Detailed explanation
Correct. Without the required privilege, the requested negative adjustment is rejected.
Correct. Without the required privilege, the requested negative adjustment is rejected.
Incorrect. Ordinary users cannot universally raise priority without permission.
Incorrect. Ordinary users cannot universally raise priority without permission.
Incorrect. A positive 5 would be a different, lower-priority adjustment.
Incorrect. A positive 5 would be a different, lower-priority adjustment.
Incorrect. nice applies to the newly started worker, not the current Bash.
Incorrect. nice applies to the newly started worker, not the current Bash.
Try it yourself
An example you can run in a temporary verification environment.
権限構成に依存するため、負のnice値を実際には設定せず仕様だけを確認Expected result
一般ユーザー・追加許可なしでは要求した負の調整が拒否されるKey points
- Negative adjustment moves toward higher priority
- Ordinary users are restricted
- Positive adjustments are normally allowed
Notes
- Environment: Linuxの通常権限モデル
- Command output formatting can vary slightly by distribution or tool version.
- Run the example in a temporary directory or process when possible.
Foundation review
Read the scope first
Check whether the command acts on the current shell, a new process, an existing process, or a file.
Verify the observable result
Use the supplied command and compare the output with the expected result.