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

gluon-quickfix: check for respondd or alfred #16

Open
rubo77 opened this issue May 3, 2017 · 6 comments
Open

gluon-quickfix: check for respondd or alfred #16

rubo77 opened this issue May 3, 2017 · 6 comments

Comments

@rubo77
Copy link
Collaborator

rubo77 commented May 3, 2017

in some communities they still use alfred instead, there would have to be a check, if respondd is installed before you use the check if it is still running

@Adorfer
Copy link
Member

Adorfer commented May 4, 2017

  1. What is "gluon-quickfix"?
  2. if alfred is used, it's just a wrapper calling for respondd via a cronjob.
  3. for communities without respondd (like babel?) theses packages do not work.

@rubo77
Copy link
Collaborator Author

rubo77 commented May 4, 2017

@Adorfer
Copy link
Member

Adorfer commented May 5, 2017

this one I did not use yet.
personally I do not like the idea of rebooting after the first error.
there should be at least a single retry after 30s.

@rubo77
Copy link
Collaborator Author

rubo77 commented May 5, 2017

It is about "not rebooting" Düring the first hour

@rubo77
Copy link
Collaborator Author

rubo77 commented May 5, 2017

Or what do you mean by"retry"?

@Adorfer
Copy link
Member

Adorfer commented May 5, 2017

If for example respondd or dropbear is not present, i do not want an instant reboot.
for example if somebody is just restarting dropbear or respondd just that very moment during the check, the node would then reboot instantly.

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

No branches or pull requests

2 participants