I agree with Mikkel. I use 13.10 and I find every day that my machine
becomes completely unusable for around 15 minutes or so because of
updatedb. This is not behaviour I used to get when I was using Windows,
and I have never heard a Mac user complain about anything like this.
--
You received
locate/updatedb/findutils is *destroying* my laptop on a daily basis.
Recent Ubuntu releases (in particular after 12.04) seem to have gotten
particularly suceptible to UI hangs under heavy IO load. This makes
Unity (and all other desktop systems I've tried) unusable for ~20
minutes each day.
--
Why hasn't this been done? This is the one issue that has me wanting to
throw Ubuntu out the window. Every morning at 8am it eats my hard drive
for breakfast for more than 10 minutes straight. And for what? I've
tried using ubnutu's search feature and it never finds any thing. So
what the f is it
Are you referring to a graphical search feature (which should have its own
indexing process) or the locate command?
You can change the configuration on your own system until a decision is made
on this issue.
Maco
On Oct 9, 2011 8:01 AM, trans 271...@bugs.launchpad.net wrote:
Why hasn't this
The optimal solution of course would be an incremental database update - only
change stuff that actually *does* change, and don't rescan all filesystems of
which 99% are unchanged between updates. But what's missing there is a decent
idea on how to make sure all filesystem changes are
On Thu, Sep 10, 2009 at 04:19:15AM -, Kevin Hunter wrote:
One issue for me is the fact that I use my laptop's battery a LOT. The
cron job for this isn't currently smart enough to realize that I'm on a
battery and not run that job.
I thought we fixed that a while back - can you attach your
Huh. Sho' nuff. I have a similar fragment:
if which on_ac_power /dev/null 21; then
AC_POWER=0
on_ac_power /dev/null 21 || AC_POWER=$?
if [ $AC_POWER -eq 1 ]; then
echo 2 On battery power, not running today.
exit 1
fi
fi
At first glance and trial, the logic
One issue for me is the fact that I use my laptop's battery a LOT. The
cron job for this isn't currently smart enough to realize that I'm on a
battery and not run that job. Reducing to once a week would help my
particular situation, as it takes about 15-20 minutes of continuous
spinning to
I think this should remain a daily cron job. If you can't trust locate
to be at least halfway up-to-date you could just use find instead, or
you'd be always forced to run updatedb before using locate. This would
mitigate locate's benefits.
OTOH I don't believe that reducing reads in any way would
Marking this confirmed because weekly would be easier on hard drives,
and it is currently daily.
** Changed in: mlocate (Ubuntu)
Status: New = Confirmed
--
updatedb should be weekly, not daily
https://bugs.launchpad.net/bugs/271272
You received this bug notification because you are a
A further optimization might be to separate updates into dev sections.
Clearly, not everyone separates their data from their system, but for
those who do, being able to scan just the /home dir would also reduce
the wear-and-tear further.
Then, though it makes the mlocate script a little more
An apt-file tie-in could make it not have to even do index updating for
apt. If there's some way to get data from apt-file to the index, that
is.
--
updatedb should be weekly, not daily
https://bugs.launchpad.net/bugs/271272
You received this bug notification because you are a member of Ubuntu
Point. On the other hand, I'm suggesting a small incremental
improvement.
In order of difficulty:
1. Move mlocate to /etc/cron.weekly/. (Very easy.)
2. Only update system dirs (i.e. /) if dpkg has been run. (Easy.)
3. Split updates of / and /home. (Hard.)
4. Update system dirs when dpkg is
Tracker's in charge of home directories anyway, right? So no real need
for having both locate *and* tracker index them. Ignore for the moment
that I disable tracker due to knowing where my files are.
--
updatedb should be weekly, not daily
https://bugs.launchpad.net/bugs/271272
You received
Heh. Right there with you. Tracker takes too many resources for me,
even on this dual core 2.2 Ghz with 4GB ram, so I too have disabled it.
But, for the vast majority of folks who won't disable it -- or when
tracker graduates to less of a resource hog and a more mature product
overall -- that's
** Changed in: mlocate (Ubuntu)
Sourcepackagename: anacron = mlocate
--
updatedb should be weekly, not daily
https://bugs.launchpad.net/bugs/271272
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
16 matches
Mail list logo
