Description
Not too important.
A user showed a particular failure scenario where shutdown was called twice, and additionally two sedfile errors that came afterwards, but it should have stopped from the first shutdown.
The function involved likely continues running instead of exiting early on failure. This may be the case for other scripts that invoke shutdown on failure. A workaround could just involve the logger being aware of the shutdown call to silence it's logging from then on? 🤷♂️
Or we can just leave it as-is. I believe there's some desired changes in future for running bash scripts that handle failure better? Or the potential that we migrate away from bash scripts.
Description
Not too important.
A user showed a particular failure scenario where shutdown was called twice, and additionally two
sedfileerrors that came afterwards, but it should have stopped from the first shutdown.The function involved likely continues running instead of exiting early on failure. This may be the case for other scripts that invoke shutdown on failure. A workaround could just involve the logger being aware of the shutdown call to silence it's logging from then on? 🤷♂️
Or we can just leave it as-is. I believe there's some desired changes in future for running bash scripts that handle failure better? Or the potential that we migrate away from bash scripts.