slocate cron job fails without ioprio_set
Bug #173489 reported by
Matt LaPlante
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
slocate (Ubuntu) |
Invalid
|
Low
|
Unassigned |
Bug Description
Binary package hint: slocate
I have gutsy installed on an openvz virtual machine (from a vps provider). Apparently these VMs do not include the ioprio_set ability, because my slocate cron job fails daily:
/etc/cron.
ioprio_set: Operation not permitted
I can confirm that the 'ionice' command is effectively useless on this installation, as it pretty much always fails with the above. The cron job needs to find a way around this or else slocate will never be updated without manual intervention.
To post a comment you must log in.
This seems to be only an error from ionice, but updatedb will run nevertheless, because ionice should get called for the current process only: PRIORITY: -7} -p $$
ionice -c ${IONICE_CLASS:-2} -n ${IONICE_
I've found http:// bugs.debian. org/cgi- bin/bugreport. cgi?bug= 456292 which talks about this for dlocate (where it really fails, because ionice calls the command) and the solution appears to be redirecting stderr for the ionice call to /dev/null.
Can you report it for slocate to Debian and then link it here?
Because it's only a cosmetical thing, I don't think we should risk doing this differently than in Debian.