Debian runs automatically (every day) a program named `updatedb' which builds
some sort of file database. To disable this you can simply chmod 644
/etc/cron.daily/find.
-Lex
On Tue, Jun 08, 1999 at 08:47:38AM -0700, Martin Waller wrote:
> It's happened to me before (under hamm, but not slink) and
> "locate" command. It walks through the entire filesystem, so thats why
> the disk runs for so long. :)
> > > > Hey, my hard drive did the sudden thrashing thing last night too. Its
> > > > never done it before (well it has in NT but not in Linux). All I was
It's probably worth mentioning at thi
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On Tue, 08 Jun 1999 08:47:38 PDT, Martin Waller wrote:
>I don't why it ran find but it was a pain in the ass.
It is the locate database updating. Want a real PITA, try an out of date
locate database. ;)
- --
Steve C. Lamb | I
Martin Waller wrote:
> It's happened to me before (under hamm, but not slink) and it was find
> running.
>
> I don't why it ran find but it was a pain in the ass.
See the `locate' command. It's very handy to quickly find files
on your system:
$ locate bib-cite.el
/usr/lib/xemacs-20.4/lisp/au
It is probably just the updatedb running, to update the database for the
"locate" command. It walks through the entire filesystem, so thats why
the disk runs for so long. :)
On Tue, 8 Jun 1999, Martin Waller wrote:
> It's happened to me before (under hamm, but not slink) and it was find
> runn
It's happened to me before (under hamm, but not slink) and it was find
running.
I don't why it ran find but it was a pain in the ass.
I haven't had the problem for a while.
May be there's some process running that lokks for something in a default
loctaion and then if it can't get it there for
6 matches
Mail list logo
