Alessandro
My feedback
3 results found
-
3 votes
Thank you for your input! We will consider this functionality in upcoming releases if it becomes popular.
Everyone, please continue voting for this feature if you consider it important.
-- SH
An error occurred while saving the comment Alessandro
supported this idea
·
-
2 votes
Thank you for your suggestion. We will consider this functionality in upcoming releases if it is popular. Everyone, please continue voting for this feature if you consider it important.
-- KvD
Alessandro
shared this idea
·
-
1 vote
Thank you for your idea.
For the time being, please consider that a script that is started via cronjob, should check itself if another instance of the same script is already running, if there is a risk that a further instance causes problems. Crontab cannot check that.
Also, please be aware that users are not bound to repeat actions in a script in a while-loop. They can easily start a script every 10 minutes, yet let it run over and over again by just putting their content into a while-loop, maybe even wait a few seconds after each iteration. So limiting them to create cronjobs for only every n minutes will not keep users from executing scripts all the time.
We'd like to hear more from other users what they think about the idea. If it still becomes popular, it might find its way into a future version of the…
An error occurred while saving the comment Alessandro
commented
As mitigation measure I use this batch to run periodically https://github.com/carininet/cronwatch to have, at least, a notification if a crontab-launched process took too long.
Alessandro
shared this idea
·
On external S3 storage a connection drop can happen. In the event the backup should be automatically retried