Thanks to Ken and Jerry, I think it may not a cron job, because this
"find" problem comes out when CPU is idel, but actually I'm
working(reading) on the computer at that time. This "find" process needs
about 10 mins to finish, so when I go back to the console, or other
programs, I feel the computer is too too much slow. In that case, I have
to kill all the "find" process.
I don't understand Ken's suggestion. I know the "locate" and "begeal", but
what I need to find? Actually I don't which process/program invoks "find".
As for Jerry's suggestion, I checked /etc/cron.daily, none of those files
contain "-regex" which is in the "find" command line. I think this problem
is not related to the cron.daily.
Any suggestions? Thanks!
Liu
On Mon, 26 Jun 2006 14:42:55 -0300, Jerry Feldman
On Monday 26 June 2006 1:29 pm, Ken Schneider wrote:
On Mon, 2006-06-26 at 12:41 -0300, JunJun Liu wrote:
Hi everybody,
I've SUSE10 installed in my personal computer. I'm always being bothered by a "find" process. It makes the computer very very slow when I'm working(reading something). I have to kill the find process by hand everyday! It looks like a system schedule. But I can't find it out :( Can anybody here please help me disable this "find"? Thanks in advance!
Actually what you want to look for are either "beagle" or "locate" that index files on the PC. Actually, I think that JunJun's finds are one of the SuSE cron jobs in /etc/cron.daily, and it is getting hung up, but there is also a beagle cron in there.
-- JunJun Liu College of Chemistry Central China Normal University WuHan 430079 P.R. China -- Check the headers for your unsubscription address For additional commands send e-mail to suse-linux-e-help@suse.com Also check the archives at http://lists.suse.com Please read the FAQs: suse-linux-e-faq@suse.com