Skip to content
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

Exit on error #29

Merged
merged 1 commit into from
Nov 6, 2024
Merged

Exit on error #29

merged 1 commit into from
Nov 6, 2024

Conversation

myhro
Copy link
Contributor

@myhro myhro commented Nov 6, 2024

If the main Unison process exits, e.g. when the SSH connection is dropped, fsmonitor keeps printing errors in an infinite loop. This, in turn, uses tons of CPU and memory, to the point of exhausting system resources. Exiting whenever it detects an error prevents this issue.

Closes #27. This is an implementation of the fix suggested in the same issue.

If the main Unison process exits, e.g. when the SSH connection is
dropped, fsmonitor keeps printing errors in an infinite loop. This, in
turn, uses tons of CPU and memory, to the point of exhausting system
resources. Exiting whenever it detects an error prevents this issue.
@autozimu autozimu merged commit 9828ab8 into autozimu:master Nov 6, 2024
1 of 3 checks passed
@autozimu
Copy link
Owner

autozimu commented Nov 6, 2024

Thank you!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

High CPU/memory usage after main unison process exits
2 participants