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

Installer adds burst #28

Closed
immesys opened this issue Jun 23, 2017 · 1 comment
Closed

Installer adds burst #28

immesys opened this issue Jun 23, 2017 · 1 comment

Comments

@immesys
Copy link
Member

immesys commented Jun 23, 2017

It would be better if the installer did not specify startlimitinterval and burst otherwise if there is some failure (e.g a powercut in soda) then spawnpoints will not start up afterwards because they will enter systemd failed mode.

@jhkolb
Copy link
Contributor

jhkolb commented Oct 13, 2017

Lol, I'm pretty sure I added these in after the bandwidth fiasco at the garber deployment (which ended up being mongo and not spawnd anyways).

I've removed them, so future installs won't include StartLimitInterval or StartLimitBurst in their unit files. And, these fields will be removed from existing unit files when you use the installer to update spawnd as well.

@jhkolb jhkolb closed this as completed Oct 13, 2017
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