My feedback

2 results found

1. Database views should be saved and restored correctly

   1 vote

   Vote Vote Vote

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   Vote

   We’ll send you updates on this idea

   0 comments  ·  Feature Suggestions » Backup / Restore  ·  Edit…  ·  Delete…  ·  Admin →
   How important is this to you?

   Not at all You must login first! Important You must login first! Critical You must login first!

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close
   Alessandro shared this idea  ·  April 13, 2024

2. Limit maximum crontab frequency and preventing cronjobs pile-up

   1 vote

   Vote Vote Vote

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   Vote

   We’ll send you updates on this idea

   1 comment  ·  Feature Suggestions » Plesk (general)  ·  Delete…  ·  Admin →
   How important is this to you?

   Not at all You must login first! Important You must login first! Critical You must login first!

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close
   open discussion  ·  AdminPlesk Staff (Community Manager, Plesk International GmbH) responded

   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 product.

   -- PD

   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… more

   An error occurred while saving the comment
   Alessandro commented  ·  February 29, 2024  ·  Edit…  ·  Delete…

   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.

   Save Submitting...
   Alessandro shared this idea  ·  February 27, 2024