Since a cron job lists the timeframe in which a task will run incrementally using the minute, hour, day, month and day of the week settings, it seems difficult to process a task more than once a minute. <\/p>\n
This can be overcome by using a simple shell script that repeatedly runs the task, with a sleep command between each call to the job. Lets say for some reason you want to clear the mail queue every 30 seconds;<\/p>\n
This will run the task two times over the course of a minute (not allowing for processing time). you will then create a cron entry to call the above script, with the minute interval set to “every minute” (*\/1).<\/p>\n (btw, this would not be a good idea in case you were thinking “Oh WOW, I can so use this…”)<\/p>\n This will allow the command to run every 30 seconds as opposed to one minute. You can use your imagination here to setup a cron executing a script that runs more than once per minute. <\/p>\n An example off the top of my head would be to take a snapshot via a webcam every 10 seconds to do time lapse photography (not that you would want to use a webcam for photography… just an example)<\/p>\n","protected":false},"excerpt":{"rendered":" Since a cron job lists the timeframe in which a task will run incrementally using the minute, hour, day, month and day of the week settings, it seems difficult to process a task more than once a minute. This can be overcome by using a simple shell script that repeatedly runs the task, with a… <\/p>\n
\n#!\/bin\/sh
\nfor i in `exim -bpr|awk {'print $3'}`;do \/usr\/sbin\/exim -v -Mrm $i;done
\nsleep 30
\nfor i in `exim -bpr|awk {'print $3'}`;do \/usr\/sbin\/exim -v -Mrm $i;done
\nsleep 30
\n<\/code><\/p>\n