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 have seen an issue related to the "reboot" request in System Services. An application on a STB is making this request after encountering a major error, in this case failing to launch the EPG (UI) app.
The application is started and managed by systemd. It expects to receive a SIGTERM signal to do a graceful shutdown. However, no SIGTERM is received by the application after the reboot request. Hence it is unable to do a graceful shutdown before reboot. This can sometimes results in a core dump file.
Can someone tell me if System Services does do a shutdown vis-à-vis systemd? It doesn't appear to be doing that. Otherwise I would expect to receive the SIGTERM signal from systemd.
The text was updated successfully, but these errors were encountered:
Hi,
I have seen an issue related to the "reboot" request in System Services. An application on a STB is making this request after encountering a major error, in this case failing to launch the EPG (UI) app.
The application is started and managed by systemd. It expects to receive a SIGTERM signal to do a graceful shutdown. However, no SIGTERM is received by the application after the reboot request. Hence it is unable to do a graceful shutdown before reboot. This can sometimes results in a core dump file.
Can someone tell me if System Services does do a shutdown vis-à-vis systemd? It doesn't appear to be doing that. Otherwise I would expect to receive the SIGTERM signal from systemd.
The text was updated successfully, but these errors were encountered: