Re: missed cron jobs
On Thu, May 15, 1997 at 04:38:11PM +0200, E.L. Meijer (Eric) wrote: > running `find' (it's amazing, isn't it ? :). I soon realized that this > was cron running the cron.daily scripts. I never thought about this > before, but it may very well have been the first time these scripts > were run, my computer at home is usually switched off at this time. > Now comes my question: > > Could this be harmful? > > I think a lot of people using linux at home don't leave their computer > switched on continuously. Has anyone ever thought of a system that > would spot missed cron events and run them at a later time? Would this > be useful at all? anacron does this very nicely. From memory, when first installed (it is available for debian) it doesn't actually do anything, but it is easy enough to move the cron.daily, weekly, monthly scripts to run from anacron instead of cron; then things get run once a day only, but definatel (if the PC is used at all that day). Very nice. Hamish -- Hamish Moffatt, StudIEAust[EMAIL PROTECTED] Student, computer science & computer systems engineering.3rd year, RMIT. http://yallara.cs.rmit.edu.au/~moffatt (PGP key here) CPOM: [ ] 45% -- TO UNSUBSCRIBE FROM THIS MAILING LIST: e-mail the word "unsubscribe" to [EMAIL PROTECTED] . Trouble? e-mail to [EMAIL PROTECTED] .
Re: missed cron jobs
On Thu, 15 May 1997, E.L. Meijer (Eric) wrote: > This morning I worked on my home debian system at a very early time > (for me, that is), from 6:30 a.m on. All of a sudden my hard disk > begins to crackle, opening a new window takes longer than normal (I > have a lowly 486DX100), and after starting top I see that `nobody' is -- It's not actually harmful. Debian runs a cron job daily, at around 6:42 a.m. and one of the invoked is a find script. This script grinds your harddisk for all files in your harddisk and puts it in a file called locatedb. Very useful if you use the program locate a lot (like me.). > I think a lot of people using linux at home don't leave their computer > switched on continuously. Has anyone ever thought of a system that > would spot missed cron events and run them at a later time? Would this > be useful at all? none that i can think of. But you can reschedule your cronjobs at a time where you usually use your computer. regards, =-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-= Andre M. Varon Lasaltech, Incorported Technical Head Fax-Tel: (034)433-3520 e-mail : [EMAIL PROTECTED] web page: http://www.lasaltech.com/andre.html =-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-= -- TO UNSUBSCRIBE FROM THIS MAILING LIST: e-mail the word "unsubscribe" to [EMAIL PROTECTED] . Trouble? e-mail to [EMAIL PROTECTED] .
Re: missed cron jobs
On May 15, E.L. Meijer (Eric) wrote > This morning I worked on my home debian system at a very early time > (for me, that is), from 6:30 a.m on. All of a sudden my hard disk > begins to crackle, opening a new window takes longer than normal (I > have a lowly 486DX100), and after starting top I see that `nobody' is > running `find' (it's amazing, isn't it ? :). I soon realized that this > was cron running the cron.daily scripts. I never thought about this > before, but it may very well have been the first time these scripts > were run, my computer at home is usually switched off at this time. > Now comes my question: > > Could this be harmful? Well, AFAIK it's not going to harm your system, but it does fairly useful things like rotating logfiles and removing old catpages. It also rebuilds the dwww cache if you have that installed, and checks some security things (most of which are more useful if you're on a network). > I think a lot of people using linux at home don't leave their computer > switched on continuously. Has anyone ever thought of a system that > would spot missed cron events and run them at a later time? Would this > be useful at all? See the `anacron' package, which does just this. It can be run at bootup and from cron, and if it hasn't been run yet that day, executes the scripts. So you can turn your machine on, and go and have breakfast, and come back when it's done! (I too have a lowly 486 :) &E -- Andy Mortimer, [EMAIL PROTECTED] http://www.netforward.com/poboxes/?andy.mortimer Finger [EMAIL PROTECTED] for PGP public key -- She talked about the armies that marched inside her head, And how they made her dreams go bad. But oh how happy she was, How proud she was, to be fighting in the war. In the empty world. -- TO UNSUBSCRIBE FROM THIS MAILING LIST: e-mail the word "unsubscribe" to [EMAIL PROTECTED] . Trouble? e-mail to [EMAIL PROTECTED] .
Re: missed cron jobs
John Maheu ([EMAIL PROTECTED]) wrote: : My computer is at home and I have noticed the noisy disk activity to. It : seems to be associated with syslogd being restarted. : May 15 06:43:35 macrae syslogd 1.3-0#13: restart. : : How can I schedule this job for a more appropriate time? Sure. Just edit /etc/crontab and change the time for the dayly, weekly and monthly cron jobs. E.- -- Eloy A. Paris Information Technology Department Rockwell Automation de Venezuela Telephone: +58-2-9432311 Fax: +58-2-9430323 -- TO UNSUBSCRIBE FROM THIS MAILING LIST: e-mail the word "unsubscribe" to [EMAIL PROTECTED] . Trouble? e-mail to [EMAIL PROTECTED] .
Re: missed cron jobs
On Thu, 15 May 1997, E.L. Meijer (Eric) wrote: > This morning I worked on my home debian system at a very early time > (for me, that is), from 6:30 a.m on. All of a sudden my hard disk > begins to crackle, opening a new window takes longer than normal (I > have a lowly 486DX100), and after starting top I see that `nobody' is > running `find' (it's amazing, isn't it ? :). I soon realized that this > was cron running the cron.daily scripts. I never thought about this > before, but it may very well have been the first time these scripts > were run, my computer at home is usually switched off at this time. > Now comes my question: > > Could this be harmful? > > I think a lot of people using linux at home don't leave their computer > switched on continuously. Has anyone ever thought of a system that > would spot missed cron events and run them at a later time? Would this > be useful at all? > > Eric Meijer > > -- My computer is at home and I have noticed the noisy disk activity to. It seems to be associated with syslogd being restarted. May 15 06:43:35 macrae syslogd 1.3-0#13: restart. How can I schedule this job for a more appropriate time? * John Maheu Queen's University Dept. of Economics Kingston ON Canada K7L 3N6 email: [EMAIL PROTECTED] ** -- TO UNSUBSCRIBE FROM THIS MAILING LIST: e-mail the word "unsubscribe" to [EMAIL PROTECTED] . Trouble? e-mail to [EMAIL PROTECTED] .
Re: missed cron jobs
On May 15, E.L. Meijer (Eric) wrote [problems when cron jobs are never executed on systems that aren't switched on 24hrs/day ?] > Could this be harmful? AFAIK: not really. It does mean that logs keep on growing, but that's easily cured. > I think a lot of people using linux at home don't leave their computer > switched on continuously. Has anyone ever thought of a system that > would spot missed cron events and run them at a later time? Would this > be useful at all? Something like that has already been implemented: Debian's "anacron" package (in unstable/admin). HTH, Ray -- Obsig: developing a new sig -- TO UNSUBSCRIBE FROM THIS MAILING LIST: e-mail the word "unsubscribe" to [EMAIL PROTECTED] . Trouble? e-mail to [EMAIL PROTECTED] .
missed cron jobs
This morning I worked on my home debian system at a very early time (for me, that is), from 6:30 a.m on. All of a sudden my hard disk begins to crackle, opening a new window takes longer than normal (I have a lowly 486DX100), and after starting top I see that `nobody' is running `find' (it's amazing, isn't it ? :). I soon realized that this was cron running the cron.daily scripts. I never thought about this before, but it may very well have been the first time these scripts were run, my computer at home is usually switched off at this time. Now comes my question: Could this be harmful? I think a lot of people using linux at home don't leave their computer switched on continuously. Has anyone ever thought of a system that would spot missed cron events and run them at a later time? Would this be useful at all? Eric Meijer -- E.L. Meijer ([EMAIL PROTECTED]) | tel. office +31 40 2472189 Eindhoven Univ. of Technology | tel. lab. +31 40 2475032 Lab. for Catalysis and Inorg. Chem. (TAK) | tel. fax+31 40 2455054 -- TO UNSUBSCRIBE FROM THIS MAILING LIST: e-mail the word "unsubscribe" to [EMAIL PROTECTED] . Trouble? e-mail to [EMAIL PROTECTED] .
