Kernel 2.0.0 goes on "find spree" at will

Kernel 2.0.0 goes on "find spree" at will

Post by Cork » Mon, 17 Mar 1997 04:00:00



Hi,

I'm running an otherwise friendly 2.0.0. kernel that insists on looking
for something it never finds; and it looks everywhere, including the
cdrom. There doesn't seem to be any pattern to when it looks, but it
only seems to do it once per "session". Here is what "ps" says when I ps
it so I can kill it. This is as much as I can read in a maximized xterm
window, it could go on for miles:

find / ( -fstype nfs -o -fstype NFS -o -type d -regex
\(^/tmp$\)\|\(^/usr/tmp$\)\|\(^/var/tmp$\)\|\(^/proc$\)\|\(^/afs$\ and
on it goes.

Everything seems to work OK.

Any suggestions?

TIA,

Corky

 
 
 

Kernel 2.0.0 goes on "find spree" at will

Post by Carrer Yuri 341353/ » Thu, 27 Mar 1997 04:00:00




>Hi,

>it so I can kill it. This is as much as I can read in a maximized xterm
>window, it could go on for miles:

 do crontab -e as root and comment out *with a #* the line in the find.

Quote:

>find / ( -fstype nfs -o -fstype NFS -o -type d -regex
>\(^/tmp$\)\|\(^/usr/tmp$\)\|\(^/var/tmp$\)\|\(^/proc$\)\|\(^/afs$\ and

--
   ol     Carrer Yuri   Pubblicita': usa \documentstyle{athenaslide}  
   |--    Tel: 0421/211239 *new*     e non usare Power Point :-)
  000 *** WARNING ***   http://www.dei.unipd.it/~carrery/
http://www.geocities.com/TheTropics/1797/  http://www.alfa.it/ :) *new!*

 
 
 

Kernel 2.0.0 goes on "find spree" at will

Post by Leslie Mikese » Thu, 27 Mar 1997 04:00:00




>I'm running an otherwise friendly 2.0.0. kernel that insists on looking
>for something it never finds; and it looks everywhere, including the
>cdrom. There doesn't seem to be any pattern to when it looks, but it
>only seems to do it once per "session". Here is what "ps" says when I ps
>it so I can kill it. This is as much as I can read in a maximized xterm
>window, it could go on for miles:

>find / ( -fstype nfs -o -fstype NFS -o -type d -regex
>\(^/tmp$\)\|\(^/usr/tmp$\)\|\(^/var/tmp$\)\|\(^/proc$\)\|\(^/afs$\ and
>on it goes.

>Everything seems to work OK.

>Any suggestions?

Most likely a cron entry for 'updatedb' which updates the database
used by the 'locate' command.  If you use 'locate', let it run so
the database will be current.

Les Mikesell