4 thoughts on - Dont Run Cron.d- When Cron.daily-scripts Are Running

• Well, this is anything but elegant, but if your daily occurs at an exact hour and minute you could write two series of per minute cron jobs (a “before’ and an “after”) avoiding that minute.

  Leroy Tennison Network Information/Cyber Security Specialist E: leroy@datavoiceint.com
  2220 Bush Dr McKinney, Texas
  75070
  http://www.datavoiceint.com This message has been sent on behalf of a company that is part of the Harris Operating Group of Constellation Software Inc. These companies are listed here
  . If you prefer not to be contacted by Harris Operating Group please notify us
  . This message is intended exclusively for the individual or entity to which it is addressed. This communication may contain information that is proprietary, privileged or confidential or otherwise legally exempt from disclosure. If you are not the named addressee, you are not authorized to read, print, retain, copy or disseminate this message or any part of it. If you have received this message in error, please notify the sender immediately by e-mail and delete all copies of the message.

• run-parts doesn’t look like it produces a lock, so I’d venture that the simplest way would be:

  */5 * * * *   root pidof -x run-parts || your-command-here

• Thats a nice solution! Pragmatic and more accurate than the path I was on. Thanks!

• I should have noted that this will avoid starting your scripts if run-parts is running, but it won’t prevent run-parts from starting while your script runs.  If that’s important, then you’ll have to modify both your cron jobs and the system crontabs that start run-parts, and use a lock of one sort or another.