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
Currently on sysvinit or upstart systems the deb will stop InstrumentalD on upgrade. This is because on first install the user doesn't have an API token in place, so the start would fail.
Ideally, if you have an API token configured the package upgrade would start the newly installed binary.
This behavior is also different with systemd. It seems like they should match, but I'm not familiar with why they differ.
The text was updated successfully, but these errors were encountered:
Currently on sysvinit or upstart systems the deb will stop InstrumentalD on upgrade. This is because on first install the user doesn't have an API token in place, so the start would fail.
Ideally, if you have an API token configured the package upgrade would start the newly installed binary.
This behavior is also different with systemd. It seems like they should match, but I'm not familiar with why they differ.
The text was updated successfully, but these errors were encountered: