user's crontab, Vixie Cron 3.0pl1-57.3), if you set a job for the next
minute, the job won't run, but will if you set it for a minute after
i.e. you write a crontab at 10:37:xx and set the job for 10:38, it
won't run - It's got to be set for 10:39.
That was my experience anyway, at did took me a while to work out why
my job wasn't running.
On Wed, May 23, 2001 at 06:03:17PM +0100, Ruairi Newman wrote:
> It does & it doesn't. It depends on the job really... if it's a job that
> uses a hell of a lot of cpu & memory when you run it manually, it's going to
> do the same when run from the crontab.
>> crond checks the crontabs every minute regardless of whether you have 1 job
> scheduled or 50, so in this respect you're not going to increase the load on
> your system.
>> ----- Original Message -----
> From: "adam beecher" <adam at iewebs.com>
> To: "CLUG" <cork at linux.ie>
> Sent: Wednesday, May 23, 2001 5:34 PM
> Subject: [CLUG] Cron job
>>> > Is there a limit to how often you can run a cron job? I know one of my
> > machines runs one every five minutes, but does that affect performance?
> Cork maillist - Cork at linux.ie>http://www.linux.ie/mailman/listinfo/cork>
Maintained by the ILUG website team. The aim of Linux.ie is to
support and help commercial and private users of Linux in Ireland. You can
display ILUG news in your own webpages, read backend
information to find out how. Networking services kindly provided by HEAnet, server kindly donated by
Dell. Linux is a trademark of Linus Torvalds,
used with permission. No penguins were harmed in the production or maintenance
of this highly praised website. Looking for the
Indian Linux Users' Group? Try here. If you've read all this and aren't a lawyer: you should be!