This repository has been archived by the owner on Nov 8, 2022. It is now read-only.
Snap should restart in response to a SIGHUP #1058
Comments
tjmcs
pushed a commit
to tjmcs/snap
that referenced
this issue
Jul 8, 2016
tjmcs
pushed a commit
to tjmcs/snap
that referenced
this issue
Jul 11, 2016
tjmcs
pushed a commit
to tjmcs/snap
that referenced
this issue
Jul 11, 2016
tjmcs
pushed a commit
to tjmcs/snap
that referenced
this issue
Jul 11, 2016
tjmcs
pushed a commit
to tjmcs/snap
that referenced
this issue
Jul 11, 2016
tjmcs
pushed a commit
to tjmcs/snap
that referenced
this issue
Jul 13, 2016
tjmcs
pushed a commit
to tjmcs/snap
that referenced
this issue
Jul 13, 2016
tjmcs
pushed a commit
to tjmcs/snap
that referenced
this issue
Jul 13, 2016
tjmcs
pushed a commit
to tjmcs/snap
that referenced
this issue
Jul 13, 2016
jcooklin
added a commit
that referenced
this issue
Jul 13, 2016
Fixes #1058: Adds code to ensure Snap restarts in response to a SIGHUP
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
We should be able to use a
kill -HUP [PROC_ID](where the[PROC_ID]value is the process ID of the Snap daemon) to force the Snap daemon to restart (and pick up any changes that might have been made to the configuration in it's global configuration file).The text was updated successfully, but these errors were encountered: