[SLE] A bothering "find" in SUSE10
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! =========== liu@linux:~> ps ax| grep find 13786 ? SN 0:00 /usr/lib/find/frcode -0 13790 ? SN 0:00 su nobody -c /usr/bin/find / \( -fstype nfs -o -fstype NFS -o -fstype proc -o -fstype afs -o -fstype proc -o -fstype smbfs -o -fstype autofs -o -fstype iso9660 -o -fstype ncpfs -o -fstype coda -o -fstype devpts -o -fstype ftpfs -o -fstype devfs -o -fstype mfs -o -fstype sysfs -o -fstype shfs -o -type d -regex '\(^/mnt$\)\|\(^/cdrom$\)\|\(^/tmp$\)\|\(^/usr/tmp$\)\|\(^/var/tmp$\)\|\(^/var/spool$\)\|\(^/proc$\)\|\(^/media$\)' \) -prune -o -print0 13791 ? RN 0:10 /usr/bin/find / ( -fstype nfs -o -fstype NFS -o -fstype proc -o -fstype afs -o -fstype proc -o -fstype smbfs -o -fstype autofs -o -fstype iso9660 -o -fstype ncpfs -o -fstype coda -o -fstype devpts -o -fstype ftpfs -o -fstype devfs -o -fstype mfs -o -fstype sysfs -o -fstype shfs -o -type d -regex \(^/mnt$\)\|\(^/cdrom$\)\|\(^/tmp$\)\|\(^/usr/tmp$\)\|\(^/var/tmp$\)\|\(^/var/spool$\)\|\(^/proc$\)\|\(^/media$\) ) -prune -o -print0 ============= -- 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
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. -- Ken Schneider UNIX since 1989, linux since 1994, SuSE since 1998 -- 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
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.
--
Jerry Feldman
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
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. It might take a bit more detective work, but check the find process to find
On Monday 26 June 2006 1:01 pm, JunJun Liu wrote:
the parent process id. ('ps alx' gives you the parent process id).
--
Jerry Feldman
Thank you, Jerry. Maybe I have to wait until tomorrow to know the results
from 'ps alx'.
Regards!
Liu
On Mon, 26 Jun 2006 15:29:58 -0300, Jerry Feldman
On Monday 26 June 2006 1:01 pm, JunJun Liu wrote:
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. It might take a bit more detective work, but check the find process to find the parent process id. ('ps alx' gives you the parent process id).
-- 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
JunJun Liu wrote:
Thank you, Jerry. Maybe I have to wait until tomorrow to know the results from 'ps alx'.
probably an "updatedb" child jdd -- http://www.dodin.net http://dodin.org/galerie_photo_web/expo/index.html http://lucien.dodin.net http://fr.susewiki.org/index.php?title=Gérer_ses_photos -- 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
Hi jdd,
Why it update so frequently? Is there a way to control the time
"updating"? Thanks!
On Mon, 26 Jun 2006 15:50:03 -0300, jdd sur free
JunJun Liu wrote:
Thank you, Jerry. Maybe I have to wait until tomorrow to know the results from 'ps alx'.
probably an "updatedb" child jdd
-- 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
On Monday 26 June 2006 12:45, JunJun Liu wrote:
Hi jdd,
Why it update so frequently? Is there a way to control the time "updating"? Thanks!
It only updates once a day. Your choices are to either live with it, or uninstall findutils-locate. -- 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
I mean, can I let it updating only at night, say 2:00am?
Thanks!
On Mon, 26 Jun 2006 16:05:55 -0300, Scott Jones
On Monday 26 June 2006 12:45, JunJun Liu wrote:
Hi jdd,
Why it update so frequently? Is there a way to control the time "updating"? Thanks!
It only updates once a day. Your choices are to either live with it, or uninstall findutils-locate.
-- 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
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 The Monday 2006-06-26 at 15:04 -0300, JunJun Liu wrote:
I mean, can I let it updating only at night, say 2:00am?
It is programmed to run once every day, at the same hour as "yesterday". But, if the computer was off at the time it should have run, it will then run at the next 15 minutes mark after boot up. If you want to disable it, edit in "/etc/sysconfig/locate": RUN_UPDATEDB="no" or use Yast. Then, you either run "updatedb" manually, or the data returned by the command "locate" will be obsolete. If you want the process to run at a certain time, program a cron job to delete "/var/spool/cron/lastrun/cron.daily" about a minute before - nevertheless, if the computer is off at that time, it will then run after boot up. Another process that you might be interested is "beagle", but I know very little about it. - -- Cheers, Carlos Robinson -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.0 (GNU/Linux) Comment: Made with pgp4pine 1.76 iD8DBQFEoDqCtTMYHG2NR9URAhHmAJ0TknM1kkXJNWKoMDFK/EAGcoG3PwCcCbjb S2LF+ojH9wg7ci5/Pm20j3I= =rOMh -----END PGP SIGNATURE----- -- 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
Hi Carlos,
Thanks a lot for you detailed information! I have a further question.
According to your information below, do you mean I can set the update
running time to a certain time by run "updatedb" only once at that certain
time? For example,
1). write a cron job to run updatedb at 2:00am
2). remove crontab one day after.
Then, will "updatedb" always be running at 2:00am in the future?
Thanks!
On Mon, 26 Jun 2006 16:50:15 -0300, Carlos E. R.
It is programmed to run once every day, at the same hour as "yesterday".
-- 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
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 The Monday 2006-06-26 at 16:00 -0300, JunJun Liu wrote:
Thanks a lot for you detailed information! I have a further question. According to your information below, do you mean I can set the update running time to a certain time by run "updatedb" only once at that certain time? For example, 1). write a cron job to run updatedb at 2:00am 2). remove crontab one day after. Then, will "updatedb" always be running at 2:00am in the future?
That's not what I said. I said to remove the flag file (0 bytes): /var/spool/cron/lastrun/cron.daily about one minute before the time you want updatedb to run, ie, at 1:59 am (you can do this with an "at" job or with a "cron" job). This way, when at 2:00 am the system cronjob runs, it sees the missing flag file and thinks that the updatedb has not run, and thus runs it inmediately. In fact, it will run then all the daily jobs, not only updatedb. - -- Cheers, Carlos Robinson -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.0 (GNU/Linux) Comment: Made with pgp4pine 1.76 iD8DBQFEoFR4tTMYHG2NR9URArMTAJ9jNmkdW64pfMsymoVvE3kpFs0v7ACbB3Cl TqCotrmTI95B6Nva5/wqkkY= =B27K -----END PGP SIGNATURE----- -- 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
Thanks a lot, Carlos! I'll do it as you suggested.
Regards!
Liu
On Mon, 26 Jun 2006 18:41:03 -0300, Carlos E. R.
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1
The Monday 2006-06-26 at 16:00 -0300, JunJun Liu wrote:
Thanks a lot for you detailed information! I have a further question. According to your information below, do you mean I can set the update running time to a certain time by run "updatedb" only once at that certain time? For example, 1). write a cron job to run updatedb at 2:00am 2). remove crontab one day after. Then, will "updatedb" always be running at 2:00am in the future?
That's not what I said. I said to remove the flag file (0 bytes):
/var/spool/cron/lastrun/cron.daily
about one minute before the time you want updatedb to run, ie, at 1:59 am (you can do this with an "at" job or with a "cron" job). This way, when at 2:00 am the system cronjob runs, it sees the missing flag file and thinks that the updatedb has not run, and thus runs it inmediately. In fact, it will run then all the daily jobs, not only updatedb.
- -- Cheers, Carlos Robinson
-----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.0 (GNU/Linux) Comment: Made with pgp4pine 1.76
iD8DBQFEoFR4tTMYHG2NR9URArMTAJ9jNmkdW64pfMsymoVvE3kpFs0v7ACbB3Cl TqCotrmTI95B6Nva5/wqkkY= =B27K -----END PGP SIGNATURE-----
-- 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
On Monday 26 June 2006 22:41, Carlos E. R. wrote:
That's not what I said. I said to remove the flag file (0 bytes): /var/spool/cron/lastrun/cron.daily about one minute before the time you want updatedb to run, ie, at 1:59 am (you can do this with an "at" job or with a "cron" job). This way, when at 2:00 am the system cronjob runs, it sees the missing flag file and thinks that the updatedb has not run, and thus runs it inmediately. In fact, it will run then all the daily jobs, not only updatedb.
Useful info, Carlos - thanks. For the life of me I can't understand why there is this rat's nest of scripts, with such an unintuitive way to decide when they ought to be run - I thought one of the benefits of cron was supposed to be its simplicity, but this is hidden away here under multiple layers. The user is expected to work out that in order to run these tasks at a particular time, he has to set up a cronjob to delete a file that says they haven't been done yet??? It's logic, Jim, but not as we know it.... Why can't there be a page at install time, or a module in YaST, saying "Your PC will need to carry out some housekeeping tasks from time to time - select a time of the day when you would like these done"? I sometimes think the SUSE engineers believe it's cool to be obscure for the sake of it, and useability suffers. -- Pob hwyl / Best wishes Kevin Donnelly www.kyfieithu.co.uk - KDE yn Gymraeg www.eurfa.org.uk - Geiriadur rhydd i'r Gymraeg www.rhedadur.org.uk - Rhedeg berfau Cymraeg www.cymrux.org.uk - Linux Cymraeg ar un CD
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 The Tuesday 2006-06-27 at 12:34 +0100, Kevin Donnelly wrote:
Useful info, Carlos - thanks. For the life of me I can't understand why there is this rat's nest of scripts, with such an unintuitive way to decide when they ought to be run - I thought one of the benefits of cron was supposed to be its simplicity, but this is hidden away here under multiple layers. The user is expected to work out that in order to run these tasks at a particular time, he has to set up a cronjob to delete a file that says they haven't been done yet??? It's logic, Jim, but not as we know it....
Well, the thing is, cron is designed for systems that stay continuously on, but that is not the case for most home users (and business users should power off their computers when not used for the environment sake). The method used by SuSE ensure that any script stored in /etc/cron.daily/ once a day, although at a not easily known hour. If the computer is on continuously, then it will run every day at the same time; if it is on now and then, it will run soon after 24 hours have passed since the last time, (within 15' of power up). It has been so since I have known SuSE around version 5.2, but with some variations in the code. Have a look at '/usr/lib/cron/run-crons' for some info. The alternative would be to use "anacron" instead, but that is not even included in the distro.
Why can't there be a page at install time, or a module in YaST, saying "Your PC will need to carry out some housekeeping tasks from time to time - select a time of the day when you would like these done"? I sometimes think the SUSE engineers believe it's cool to be obscure for the sake of it, and useability suffers.
People that need to know it, do know it ;-) Otherwise, you ask here, or browse the archive, it's been commented "hundreds" of times :-p But true, it could be clearly documented, or configured in Yast. There are settings in Yast to adjust it, in fact. - -- Cheers, Carlos Robinson -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.0 (GNU/Linux) Comment: Made with pgp4pine 1.76 iD8DBQFEoaaQtTMYHG2NR9URAthQAJ0e1/6yKdLgkO/n0nPVcAp9xWbgCgCcD9bb 9EBevwZppL9rtazd9Un0n4k= =PDj0 -----END PGP SIGNATURE----- -- 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
On Tuesday 27 June 2006 22:43, Carlos E. R. wrote:
Well, the thing is, cron is designed for systems that stay continuously on, but that is not the case for most home users (and business users should power off their computers when not used for the environment sake).
I can see the rationale, but it doesn't hold water. If the system is not on continuously, it is inherently less likely that the tasks need to be run every 24 hours, so why not let the user choose when he/she wants to run them?
It has been so since I have known SuSE around version 5.2, but with some variations in the code. Have a look at '/usr/lib/cron/run-crons' for some info.
I have - that's why I called it a rat's nest :-)
Why can't there be a page at install time, or a module in YaST, saying "Your PC will need to carry out some housekeeping tasks from time to time - select a time of the day when you would like these done"? I sometimes think the SUSE engineers believe it's cool to be obscure for the sake of it, and useability suffers.
People that need to know it, do know it ;-)
Say what??? Awareness through obscurity?? That's what I was getting at, the idea that you have to be some sort of initiate to know the nous.
Otherwise, you ask here, or browse the archive, it's been commented "hundreds" of times :-p
Well, I've been on this list since 98, and I don't really remember it coming up all that often before, but maybe I'm getting old.
But true, it could be clearly documented, or configured in Yast. There are settings in Yast to adjust it, in fact.
LOL. These settings (/etc/sysconfig Editor -> Applications -> Locate) allow you to run it or not, who to run it as, and what paths to include or skip, but nothing as obvious as a time to run it at, which was the OP's problem. That's my point - it can't be harder to code a time setting than it is to code one of these settings, and yet nobody seems to have thought to do it :-) -- Pob hwyl / Best wishes Kevin Donnelly www.kyfieithu.co.uk - KDE yn Gymraeg www.eurfa.org.uk - Geiriadur rhydd i'r Gymraeg www.rhedadur.org.uk - Rhedeg berfau Cymraeg www.cymrux.org.uk - Linux Cymraeg ar un CD -- 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
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 The Wednesday 2006-06-28 at 13:13 +0100, Kevin Donnelly wrote:
On Tuesday 27 June 2006 22:43, Carlos E. R. wrote:
Well, the thing is, cron is designed for systems that stay continuously on, but that is not the case for most home users (and business users should power off their computers when not used for the environment sake).
I can see the rationale, but it doesn't hold water. If the system is not on continuously, it is inherently less likely that the tasks need to be run every 24 hours, so why not let the user choose when he/she wants to run them?
Many (new) users would not know how to program it, nor the need to do it. As it is, it works. For example, if the computer is off for a week, it will run when powered up again. If it is on full time, it will not run oftener than once a day. It's just that, an engineering compromise, a solution that works in all possible situations, even if not optimum for many.
People that need to know it, do know it ;-)
Say what??? Awareness through obscurity?? That's what I was getting at, the idea that you have to be some sort of initiate to know the nous.
I'm (half) joking. If you are an expert, you know how it works and how to modify it. If you don't know how, you probably also do not need to touch it.
Otherwise, you ask here, or browse the archive, it's been commented "hundreds" of times :-p
Well, I've been on this list since 98, and I don't really remember it coming up all that often before, but maybe I'm getting old.
Again, I'm joking. It's been commented quite often, that I know, but not "hundreds" :-)
But true, it could be clearly documented, or configured in Yast. There are settings in Yast to adjust it, in fact.
LOL. These settings (/etc/sysconfig Editor -> Applications -> Locate) allow you to run it or not, who to run it as, and what paths to include or skip, but nothing as obvious as a time to run it at, which was the OP's problem.
No, not the time. But it can be disabled there, instead of killing the job somehow, as some suggested. And there are other jobs like logrotate, tmp purge, etc, that can be adjusted.
That's my point - it can't be harder to code a time setting than it is to code one of these settings, and yet nobody seems to have thought to do it :-)
The trick of deleting the flag file is a "hack", but it works. Another better way would be to modify "/etc/crontab": - -*/15 * * * * root test -x /usr/lib/cron/run-crons && /usr/lib/cron/run-crons >/dev/null 2>&1 it would be very simple to program it at a fixed hour, or a range of hours. Very simple, and easy to find the modification for a new admin. This could be documented somewhere, of course; but the SuSE manual does not teach Linux, that is assumed. Probably they thought that admins would know, and the rest do not need to know - you know, you can not break what you don't know it exists :-P - -- Cheers, Carlos Robinson -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.0 (GNU/Linux) Comment: Made with pgp4pine 1.76 iD8DBQFEopHutTMYHG2NR9URAvYIAJ4kpcTrt8+kyVed64koFzV5HcQL2wCfdAx9 fG2E8wseteCpma/UkJyW/qI= =HsHo -----END PGP SIGNATURE----- -- 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
On Wednesday 28 June 2006 15:27, Carlos E. R. wrote: <large snip>
it would be very simple to program it at a fixed hour, or a range of hours. Very simple, and easy to find the modification for a new admin. This could be documented somewhere, of course; but the SuSE manual does not teach Linux, that is assumed.
As I said, that's my point. For a server system, where you can assume that the user will be taking the time to examine the ins and outs of various apps as a learning exercise, this makes complete sense. For a desktop system, where the user wants something to work well while he gets a job done, it makes virtually no sense - if a process is important enough to run every day, it's important enough to tell the user about, and give him an option to change. It's the difference between running a computer as an end in itself (eg webhost or mailserver or IT support), and running a computer as a tool to (say) get your graphics project finished. I don't see anything wrong with making these things configurable. -- Pob hwyl / Best wishes Kevin Donnelly www.kyfieithu.co.uk - KDE yn Gymraeg www.eurfa.org.uk - Geiriadur rhydd i'r Gymraeg www.rhedadur.org.uk - Rhedeg berfau Cymraeg www.cymrux.org.uk - Linux Cymraeg ar un CD -- 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
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 The Wednesday 2006-06-28 at 17:01 +0100, Kevin Donnelly wrote:
change. It's the difference between running a computer as an end in itself (eg webhost or mailserver or IT support), and running a computer as a tool to (say) get your graphics project finished. I don't see anything wrong with making these things configurable.
But it is configurable: you just have to change the cron line to make it run at the time frame you want. That's just standard unix/linux. I don't see necesary to move that to yast, but it could be done, I suppose. - -- Cheers, Carlos Robinson -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.0 (GNU/Linux) Comment: Made with pgp4pine 1.76 iD8DBQFEowTPtTMYHG2NR9URAhCdAJ0XfQ/sAeOEEq1nBuGYYtGJ78XXSACeJh1C vHu0mVQsEXdVY383/oayrtw= =2d/k -----END PGP SIGNATURE----- -- 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
Kevin, On Wednesday 28 June 2006 05:13, Kevin Donnelly wrote:
On Tuesday 27 June 2006 22:43, Carlos E. R. wrote:
Well, the thing is, cron is designed for systems that stay continuously on, but that is not the case for most home users (and business users should power off their computers when not used for the environment sake).
I can see the rationale, but it doesn't hold water. If the system is not on continuously, it is inherently less likely that the tasks need to be run every 24 hours, so why not let the user choose when he/she wants to run them?
That argument is the thing that does not "hold water." The number of hours per day that the system runs does not affect its need to run periodic maintenance and / or diagnostic tasks. And in fact, the system is adaptive and when it finds that it has not run the tasks on schedule, it runs them when it can. Unfortunately, for systems that are only powered on when used, this has a strong tendency to cause the periodic tasks to interfere with the use for which the machine was powered on. I agree that it should be possible for the end user to specify when daily (or weekly) periodic tasks should execute rather than have these under-the-hood machinations as the only means of controlling the scheduling of periodic tasks.
...
-- Pob hwyl / Best wishes
Kevin Donnelly
Randall Schulz -- 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
On Mon, 2006-06-26 at 13:42 -0400, Jerry Feldman wrote:
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.
Yes but locate uses find to generate its index of files. -- Ken Schneider UNIX since 1989, linux since 1994, SuSE since 1998 -- 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
participants (8)
-
Carlos E. R. -
jdd sur free -
Jerry Feldman -
JunJun Liu -
Ken Schneider -
Kevin Donnelly -
Randall R Schulz -
Scott Jones