On Tue, Jul 04, 2006 at 01:08:08PM +0000, Gerrit Pape wrote: > On Fri, Jun 23, 2006 at 10:44:20AM +0530, Joshua N Pritikin wrote: > > I'm using bcron-run. > > > > $ cat /etc/crontab > > SHELL=/bin/sh > > PATH=/usr/local/sbin:/usr/local/bin:/sbin:/bin:/usr/sbin:/usr/bin > > > > 14 * * * * root run-parts --report /etc/cron.hourly > > 24 4 * * * root run-parts --report /etc/cron.daily > > 39 4 * * 7 root run-parts --report /etc/cron.weekly > > 54 4 1 * * root run-parts --report /etc/cron.monthly > > > > However, when I "grep run-parts /var/log/bcron/[EMAIL PROTECTED]" then I > > only see > > hourly. I don't see daily or weekly. > > > > The machine is not on 24 hours but that shouldn't matter, right?. I am > > that should matter. bcron only runs scheduled jobs if the machine is up > at that time, it doesn't catch up if the machine is booting up later.
Really? I wonder why I thought differently. Why not add "anacron" to bcron's Recommends list? -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
