Skip to content

Alessandro

My feedback

2 results found

  1. 2 votes

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    Alessandro shared this idea  · 
  2. 1 vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    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  · 

Feedback and Knowledge Base