mlocate.updatedb does not call ionice

Bug #759574 reported by gpk
22
This bug affects 4 people
Affects Status Importance Assigned to Milestone
mlocate (Ubuntu)
Fix Released
Undecided
Unassigned

Bug Description

Binary package hint: mlocate

updatedb.mlocate can cause a lot of disk activity, and it is not a time-critical process. Therefore, it should call nice and ionice so that it does not steal cycles or disk activity from foreground processes.

ProblemType: Bug
DistroRelease: Ubuntu 10.10
Package: mlocate 0.22.2-1ubuntu1
ProcVersionSignature: Ubuntu 2.6.35-28.50-generic 2.6.35.11
Uname: Linux 2.6.35-28-generic x86_64
Architecture: amd64
Date: Wed Apr 13 09:31:01 2011
InstallationMedia: Ubuntu 10.04.1 LTS "Lucid Lynx" - Release amd64 (20100816.1)
ProcEnviron:
 LANGUAGE=en_GB:en
 PATH=(custom, user)
 LANG=en_GB.UTF-8
 SHELL=/bin/bash
SourcePackage: mlocate

Revision history for this message
gpk (gpk-kochanski) wrote :
Revision history for this message
Launchpad Janitor (janitor) wrote :

Status changed to 'Confirmed' because the bug affects multiple users.

Changed in mlocate (Ubuntu):
status: New → Confirmed
Revision history for this message
David Fraser (davidf) wrote :

My mlocate script installed with the latest version in 14.04 in /etc/cron.daily calls ionice, so this can be marked done

# See ionice(1)
if [ -x /usr/bin/ionice ] &&
    /usr/bin/ionice -c3 true 2>/dev/null; then
    IONICE="/usr/bin/ionice -c3"
fi

flock --nonblock /run/mlocate.daily.lock $IONICE /usr/bin/updatedb.mlocate

Changed in mlocate (Ubuntu):
status: Confirmed → Fix Released
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.