We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
I guess this line is the problem
dynamix/source/s3-sleep/scripts/s3_sleep
Line 359 in 4d6d339
If you have a post wake up script which exits with 1 instead of 0 the condition is false, and it will execute system_down.
My last line of the post sleep script which is causing this issue uses the "Test" function, and this will set the exit code to 1.
test "$(date +%s -d "60 days ago")" -gt "$(mdcmd status | sed -n 's/sbSynced=//p')" && /usr/local/sbin/mdcmd check NOCORRECT &> /dev/null
This executes the parity check if it was older than 60 days because crone schedule does not work if the system does sleep.
The text was updated successfully, but these errors were encountered:
No branches or pull requests
I guess this line is the problem
dynamix/source/s3-sleep/scripts/s3_sleep
Line 359 in 4d6d339
If you have a post wake up script which exits with 1 instead of 0 the condition is false, and it will execute system_down.
My last line of the post sleep script which is causing this issue uses the "Test" function, and this will set the exit code to 1.
This executes the parity check if it was older than 60 days because crone schedule does not work if the system does sleep.
The text was updated successfully, but these errors were encountered: