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
I am using release 4.5.3 with a systemd service script, and I have noticed that the service waits for the whole ~90 second grace period when stopping, before it gets killed forcefully. Systemd attempts to stop a service by sending SIGTERM to its process group by default.
It seems that the callback for usage stats reporting in stats.js is not invoked if no tracker instance exists:
Hi Maciej,
I am using release 4.5.3 with a systemd service script, and I have noticed that the service waits for the whole ~90 second grace period when stopping, before it gets killed forcefully. Systemd attempts to stop a service by sending
SIGTERM
to its process group by default.It seems that the callback for usage stats reporting in
stats.js
is not invoked if notracker
instance exists:frontail/lib/stats.js
Lines 57 to 63 in 205cdbf
Due to this, signals have no effect at the end of
index.js
:frontail/index.js
Lines 159 to 165 in 205cdbf
Regards,
András
The text was updated successfully, but these errors were encountered: