user should be informed that updatedb is running

Bug #133638 reported by Nicolò Chieffo on 2007-08-20
Affects Status Importance Assigned to Milestone
slocate (Ubuntu)
Kees Cook

Bug Description

Binary package hint: slocate

I think that since updatedb is automatically launched as a cron job, it should inform the user that for sime minutes there will be intense CPU and HD usage.
Otherwise the user might think that there is something wrong

Kees Cook (kees) wrote :

The need for this should be solved now (slocate runs with low CPU and IO priority now).

Changed in slocate:
assignee: nobody → keescook
status: New → Won't Fix
markor (markoresko) wrote :

I think that reasoning for this bug are right. I myself was affected with system non responsive
and not knowing what is going on for a long time.
I even closed (and killed) all my running apps, only to find out that system is doing something
I cant stop or minimize its usage, so it would definately inform user what is going on, if we
want to stop it user from using its computer for several minutes.. while system is doing something..

Milan Bouchet-Valat (nalimilan) wrote :

In recent versions of Ubuntu, this script should no take so much time because we're using mlocate, a variant that only updates files that were modified. Working period should range from 5 seconds to one minute. Is your computer recent? Are you sure the real culprit is updatedb? You can check this with 'top' in a terminal (the first process is the most active one).

To post a comment you must log in.
This report contains Public information  Edit
Everyone can see this information.

Other bug subscribers