updatedb cron job re-nices wrong process (pid 7 by default)!
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
findutils (Ubuntu) |
Invalid
|
Medium
|
Kees Cook | ||
Gutsy |
Fix Released
|
Medium
|
Unassigned |
Bug Description
Binary package hint: findutils
I see a couple problems with the /etc/cron.
1) There's an extra space in the shebang line (cosmetic)...
#! /bin/sh
2) It's passing a priority to ionice with the -p flag, however according to the ionice man page, the -p flag specifies a pid. This causes ionice to fail to run.
cd / && nice -n ${NICE:-10} ionice -c ${IONICE_CLASS:-2} -p ${IONICE_
> ioprio_set: No such process
" -p Pass in a process pid to change an already running process. "
TEST CASE:
1) force updatedb (/etc/cron.
2) while updatedb runs, examine io priority with "ionice -p $(pidof updatedb)"
3) should report "best-effort: prio 7" (broken behavior shows "none: prio 0")
Related branches
description: | updated |
description: | updated |
Changed in findutils: | |
assignee: | nobody → pitti |
status: | Fix Released → In Progress |
I see this behavior as well. I guess the author intended to use the -n flag to ionice instead of -p.