virtlockd: treat SIGHUP like SIGUSR1

SIGHUP is commonly used to instruct a daemon to reload its config. For
now we should handle it in virtlockd just like SIGUSR1, rather than
having it kill the process.

Signed-off-by: Michael Chapman <mike@very.puzzling.org>
Signed-off-by: Michal Privoznik <mprivozn@redhat.com>
This commit is contained in:
Michael Chapman 2013-12-09 17:23:27 +11:00 committed by Michal Privoznik
parent 59d6e65d6c
commit 8355d42dd3
2 changed files with 5 additions and 3 deletions

View File

@ -590,6 +590,8 @@ virLockDaemonSetupSignals(virNetServerPtr srv)
return -1; return -1;
if (virNetServerAddSignalHandler(srv, SIGUSR1, virLockDaemonExecRestartHandler, NULL) < 0) if (virNetServerAddSignalHandler(srv, SIGUSR1, virLockDaemonExecRestartHandler, NULL) < 0)
return -1; return -1;
if (virNetServerAddSignalHandler(srv, SIGHUP, virLockDaemonExecRestartHandler, NULL) < 0)
return -1;
return 0; return 0;
} }

View File

@ -54,9 +54,9 @@ Display version information then exit.
=head1 SIGNALS =head1 SIGNALS
On receipt of B<SIGUSR1> virtlockd will re-exec() its binary, while On receipt of B<SIGUSR1> or B<SIGHUP> virtlockd will re-exec() its
maintaining all current locks and clients. This allows for live binary, while maintaining all current locks and clients. This allows
upgrades of the virtlockd service. for live upgrades of the virtlockd service.
=head1 FILES =head1 FILES