This seems to be only an error from ionice, but updatedb will run nevertheless, because ionice should get called for the current process only:
ionice -c ${IONICE_CLASS:-2} -n ${IONICE_PRIORITY:-7} -p $$
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.
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.