A maintenance shell was itself started with `nice -n 5 bash`, so its nice value is 5. Inside that shell you run `nice -n 3 ./convert.sh`. What nice value does convert.sh run with?

LPIC-1 Exam 101-500, objective 103. GNU and Unix commands hard

Machine-checked — no person has signed for it. This question was read against the source cited below by an automated pass, which found no contradiction. That is a weaker claim than it sounds: the same kind of process wrote the question, so it can confirm its own mistake.

Treat it as a good draft rather than as settled fact, and read the source below before you rely on it. It is not used in mock exams here — only questions a person has signed for are.

How these questions are written — where each question comes from, what the verification ledger records, and what happens when one is found wrong.

The options

Correct 8

Correct. The argument to -n is an increment added to the niceness the command inherits, and 5 + 3 is 8.

Not correct 3

Wrong. The value is not set absolutely; that is what renice does with an already running process.

Not correct 5

Wrong. The increment is applied, so the child does not simply keep the shell's value.

Not correct 0

Wrong. Nothing resets the niceness to the system default on exec; niceness is inherited across fork and exec.

Why

nice adjusts rather than assigns: the new niceness is the caller's niceness plus the increment, clamped to the range -20 to 19. renice, by contrast, sets an absolute value on processes that already exist. Because niceness is inherited by children, an increment applied to a shell silently applies to everything that shell subsequently starts, which is the effect being tested here.

Where this comes from

Cited
manual page nice(1)

Practise this

Reading one question is not practice. The trainer will draw a short set from objective 103 and space the ones you get wrong.

Practise LPIC-1 Exam 101-500

More questions on this objective

All questions on GNU and Unix commands

Practise LPIC-1 Exam 101-500