Re: cron.daily et al.
Paul Seelig wrote: On Fri, 17 Jan 1997, Jean Pierre LeJacq wrote: How about a (cron) job, that executed every time the machine gets booted and that checks when the cron jobs were executed for the last time. If these for were not executed for say two days (weeks, months) then they get executed regardless the actual hour, day, week of month. I second this. It is not so hard actually to change the time settings oneself. Every system administrator should be able to do so. and we are all supposed to be sysadmins, aren't we? Regards, P. *8^) So please give us a concrete solution. -=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=- Seak Teng-Fong E-mail: [EMAIL PROTECTED] Bât 507 DRFC / SPPFTel: 33 (0) 4 42256125 CE / Cadarache Fax: 33 (0) 4 42256233 13108 Saint Paul lez Durance Cedex FRANCE -=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=- -- TO UNSUBSCRIBE FROM THIS MAILING LIST: e-mail the word unsubscribe to [EMAIL PROTECTED] . Trouble? e-mail to [EMAIL PROTECTED]
Re: cron.daily et al.
On Mon, 20 Jan 1997 09:31:09 +0100 Seak, Teng-Fong ([EMAIL PROTECTED]) wrote: Paul Seelig wrote: On Fri, 17 Jan 1997, Jean Pierre LeJacq wrote: How about a (cron) job, that executed every time the machine gets booted and that checks when the cron jobs were executed for the last time. If these for were not executed for say two days (weeks, months) then they get executed regardless the actual hour, day, week of month. So please give us a concrete solution. The solution's called anacron. Check it out on your closest debian mirror. Phil. -- TO UNSUBSCRIBE FROM THIS MAILING LIST: e-mail the word unsubscribe to [EMAIL PROTECTED] . Trouble? e-mail to [EMAIL PROTECTED]
Re: cron.daily et al.
I heard of a program called anacron to solve just this problem, but I don't think it's available as a Debian package, yet. Maybe someone here knows where to get it? Otherwise, you could try comp.unix.admin or gopher. That package is in project/experimental/anacron_1.0.1-3_all.deb I install it this weekend ... and all problems were solved. --jan -- TO UNSUBSCRIBE FROM THIS MAILING LIST: e-mail the word unsubscribe to [EMAIL PROTECTED] . Trouble? e-mail to [EMAIL PROTECTED]
Re: cron.daily et al.
On Mon, 20 Jan 1997, Seak, Teng-Fong wrote: Paul Seelig wrote: On Fri, 17 Jan 1997, Jean Pierre LeJacq wrote: How about a (cron) job, that executed every time the machine gets booted and that checks when the cron jobs were executed for the last time. If these for were not executed for say two days (weeks, months) then they get executed regardless the actual hour, day, week of month. I second this. It is not so hard actually to change the time settings oneself. Every system administrator should be able to do so. and we are all supposed to be sysadmins, aren't we? So please give us a concrete solution. A concrete solution for the aspiring sysadmin is launch apropos cron at a shell prompt which gives as result crontab (5) - tables for driving cron cron (8) - daemon to execute scheduled commands and this shows you which man pages to read. Then just read them and understand their contents. After that find out where the cron scripts which are not invoked by crontab -e reside on your system and read and understand them too. You will find that the man pages you read before already point to the proper places, but you could do as well a locate cron to be sure not to miss anything. If you succeed with all the aforementioned just adapt them to your needs. Not so hard actually, is it!? Regards, P. *8^) -- Paul Seelig [EMAIL PROTECTED] African Music Archive - Institute for Ethnology and Africa Studies Johannes Gutenberg-University - Forum 6 - 55099 Mainz/Germany Our AMA Homepage in the WWW at http://www.uni-mainz.de/~bender/ -- TO UNSUBSCRIBE FROM THIS MAILING LIST: e-mail the word unsubscribe to [EMAIL PROTECTED] . Trouble? e-mail to [EMAIL PROTECTED]
cron.daily et al.
Hi, There might be a problem with the execution of the cron.daily, cron.weekly, and cron.monthly : An machines that don't run all day, these cron jobs get rarely executed. For instance, I usually use my maschine only in the evenings at home (i.e. later than 6 pm). But all cron get executed at 6pm. Therefore these cron task get never executed. How about a (cron) job, that executed every time the machine gets booted and that checks when the cron jobs were executed for the last time. If these for were not executed for say two days (weeks, months) then they get executed regardless the actual hour, day, week of month. What do you people think? --jan Jan Camenisch Institut fuer theor. Informatik Tel. +41 1 632 7412 ETH Zentrum, IFW Fax. +41 1 632 1172 CH-8092 Zurich, Switzerlande-mail: [EMAIL PROTECTED] - - URL of my hompage http://www.inf.ethz.ch/personal/camenisc -- TO UNSUBSCRIBE FROM THIS MAILING LIST: e-mail the word unsubscribe to [EMAIL PROTECTED] . Trouble? e-mail to [EMAIL PROTECTED]
Re: cron.daily et al.
On Fri, 17 Jan 1997, Jan Camenisch wrote: Hi, There might be a problem with the execution of the cron.daily, cron.weekly, and cron.monthly : An machines that don't run all day, these cron jobs get rarely executed. For instance, I usually use my maschine only in the evenings at home (i.e. later than 6 pm). But all cron get executed at 6pm. Therefore these cron task get never executed. How about a (cron) job, that executed every time the machine gets booted and that checks when the cron jobs were executed for the last time. If these for were not executed for say two days (weeks, months) then they get executed regardless the actual hour, day, week of month. I second this. --- Jean Pierre -- TO UNSUBSCRIBE FROM THIS MAILING LIST: e-mail the word unsubscribe to [EMAIL PROTECTED] . Trouble? e-mail to [EMAIL PROTECTED]
RE: cron.daily et al.
Jan Camenisch wrote: There might be a problem with the execution of the cron.daily, cron.weekly, and cron.monthly : An machines that don't run all day, these cron jobs get rarely executed. For instance, I usually use my maschine only in the evenings at home (i.e. later than 6 pm). But all cron get executed at 6pm. Therefore these cron task get never executed. How about a (cron) job, that executed every time the machine gets booted and that checks when the cron jobs were executed for the last time. If these for were not executed for say two days (weeks, months) then they get executed regardless the actual hour, day, week of month. I heard of a program called anacron to solve just this problem, but I don't think it's available as a Debian package, yet. Maybe someone here knows where to get it? Otherwise, you could try comp.unix.admin or gopher. Casper Boden-Cummins. -- TO UNSUBSCRIBE FROM THIS MAILING LIST: e-mail the word unsubscribe to [EMAIL PROTECTED] . Trouble? e-mail to [EMAIL PROTECTED]
Re: cron.daily et al.
On Jan 17, Jan Camenisch wrote [cron suggestion for machines that don't run all day] How about a (cron) job, that executed every time the machine gets booted and that checks when the cron jobs were executed for the last time. If these for were not executed for say two days (weeks, months) then they get executed regardless the actual hour, day, week of month. It looks a lot like you're reinventing the anacron package. HTH, Ray -- PATRIOTISM A great British writer once said that if he had to choose between betraying his country and betraying a friend he hoped he would have the decency to betray his country. - The Hipcrime Vocab by Chad C. Mulligan -- TO UNSUBSCRIBE FROM THIS MAILING LIST: e-mail the word unsubscribe to [EMAIL PROTECTED] . Trouble? e-mail to [EMAIL PROTECTED]
Re: cron.daily et al.
How about a (cron) job, that executed every time the
machine gets booted and that checks when the cron jobs
were executed for the last time. If these for were not
executed for say two days (weeks, months) then they
get executed regardless the actual hour, day, week of month.
I second this.
I think this could be a large problem. There can exist cron jobs that
won't work unless they are run at a special time, or they could disrupt
things if they are ran at a random bootup-time.
For example, a cron job to connect to the network and mirror a ftp site --
say it takes 2 hours, and you run it in the wee hours of morning in what's
normally your voice phone line. You don't want something like this to get
run when you just boot up the computer during the day (maybe someone else
is using the phone at that time..)
Have you looked at anacron? Maybe it can do what you want:
anacron - a cron-like program that doesn't go by time
anacron (like `anac(h)ronistic') executes jobs in a certain interval.
Therefore it is useful to schedule daily maintaining jobs, such as
cleaning /tmp, getting email from the ISP, etc.
It's also a good replacement for cron on systems, that don't run
continously 24 hours a day but are powered on and shut down several times
a day.
--
#!/usr/bin/perl -pi___Syntax:_sig.pl_location-of-netscape-program___
BEGIN{if(!$ARGV[0]){$^I=~y/_/ /;print$^I\n;exit}$^I='.bak'}# Joey Hess
s/\bnoframes\b/noFrames/g;s/\bframeset\b/frameSet/g# [EMAIL PROTECTED]
#Remove frames from Netscape forever! http://kite.ml.org/~joey/framefree.cgi
--
TO UNSUBSCRIBE FROM THIS MAILING LIST: e-mail the word unsubscribe to
[EMAIL PROTECTED] . Trouble? e-mail to [EMAIL PROTECTED]
