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.

Sign up for GitHub

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

Jump to bottom

Behavior on failure to connect on startup #7

Open
Zer0-One opened this issue Jan 25, 2017 · 0 comments
Open

Behavior on failure to connect on startup #7

Zer0-One opened this issue Jan 25, 2017 · 0 comments

Comments

@Zer0-One
Copy link
Owner

If praetor can't connect to any IRC networks, then it can't be issued commands via IRC to attempt more connects and reconnects.

If it fails to connect to any networks on startup, should the daemon exit, or should we define some kind of retry behavior? This sounds like it should be user-configurable. Maybe add an option to the config?
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
1 participant
@Zer0-One