New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Handle case where snapraid is already running #62
Comments
Thank you, I will work on this. The script will stop and alert the user via the configured notification methods. By the way, are you sure you want your jobs to run for 24h? |
No, typically not. It’s just happened when large amounts of data had moved. It’s not a common case :-)Vänliga hälsningar / Best regards,Firas DibOn 13 Jun 2023, at 10:26, Oliver Cervera ***@***.***> wrote:
Thank you, I will work on this. The script will stop and alert the user via the configured notification methods.
By the way, are you sure you want your jobs to run for 24h?
—Reply to this email directly, view it on GitHub, or unsubscribe.You are receiving this because you authored the thread.Message ID: ***@***.***>
|
auanasgheps
added a commit
that referenced
this issue
Jul 13, 2023
Implemented in dev branch. Tested and works as expected! Will close this out. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
I run this script every day, but sometimes the execution runs for over 24h, due to large changes to the data. The script should check that snapraid is available before going ahead with pausing and doing all the stuff it does
The text was updated successfully, but these errors were encountered: