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

On a connection failure, stop the reactor #22

Merged
merged 1 commit into from Jan 12, 2016
Merged

Conversation

@johnwlockwood
Copy link
Owner

johnwlockwood commented Jan 12, 2016

This gives any process manager to try again.

For now, this is only in one example to try out the technique. It seems like a good thing since it let's systemd do what it does best and not try to reproduce it. If the device this is running on
hasn't established it's network connection yet, it will be able to try again and connect when
the network is working.

This gives any process manager to try again.
@johnwlockwood

This comment has been minimized.

Copy link
Owner Author

johnwlockwood commented Jan 12, 2016

With this, the service on the PI will start responding on a NATS channel after power up, having
successfully been restarted by systemd until it was able to connect.

johnwlockwood added a commit that referenced this pull request Jan 12, 2016
On a connection failure, stop the reactor
@johnwlockwood johnwlockwood merged commit 31b95c5 into master Jan 12, 2016
2 checks passed
2 checks passed
continuous-integration/travis-ci/pr The Travis CI build passed
Details
continuous-integration/travis-ci/push The Travis CI build passed
Details
@johnwlockwood johnwlockwood deleted the connect-or-die branch Jan 15, 2016
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
1 participant
You can’t perform that action at this time.