There should be a protection against multiple simultaneous runs

[Riduidel]

I have added execution of rss2imap in the crontab of my nas (a linksys dns-323).
Unfortunately due to the large number of feeds I watch, even a delay of 1 hour is not always enough to prevent multiple runs and, as a consequence, multiple copies of the same message.
Could if be possible to have a system preventing that (I have tried using pid file in r2e shell script with no success)?

[rcarmo]

Yeah, I suppose something could be done about that… I don’t run this anymore, but when I did I used a wrapper for it. I’ll see if I can find it.

On 05 Apr 2016, at 18:56, Nicolas Delsaux notifications@github.com wrote:

I have added execution of rss2imap in the crontab of my nas (a linksys dns-323).
Unfortunately due to the large number of feeds I watch, even a delay of 1 hour is not always enough to prevent multiple runs and, as a consequence, multiple copies of the same message.
Could if be possible to have a system preventing that (I have tried using pid file in r2e shell script with no success)?

—
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub #19

[Riduidel]

I think there is another way : if there was an endless run mode, I wouldn't have to cron rss2imap, and multiple instances wouldn't stack up. So, what do you think of adding that mode to the main method?

[sdt]

Do you have pgrep on your nas @Riduidel

Would something like this work in your crontab?

pgrep r2e > /dev/null || $your_existing_r2e_command