You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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.
The text was updated successfully, but these errors were encountered:
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.
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.
The text was updated successfully, but these errors were encountered: