summary |
shortlog |
log |
commit | commitdiff |
tree
raw |
patch |
inline | side by side (from parent 1:
329c63d)
Some init systems actually expect daemons to return 0 on success.
Signed-off-by: Steve Dickson <steved@redhat.com>
if (root_uses_machine_creds)
gssd_destroy_krb5_machine_creds();
printerr(1, "exiting on signal %d\n", signal);
if (root_uses_machine_creds)
gssd_destroy_krb5_machine_creds();
printerr(1, "exiting on signal %d\n", signal);
{
/* destroy krb5 machine creds */
printerr(1, "exiting on signal %d\n", signal);
{
/* destroy krb5 machine creds */
printerr(1, "exiting on signal %d\n", signal);
wait_for_workers();
}
cleanup_lockfiles();
wait_for_workers();
}
cleanup_lockfiles();
- xlog (L_FATAL, "Caught signal %d, un-registering and exiting.", sig);
+ xlog (L_NOTICE, "Caught signal %d, un-registering and exiting.", sig);
+ exit(0);
killer (int sig)
{
statd_unregister ();
killer (int sig)
{
statd_unregister ();
- xlog_err ("Caught signal %d, un-registering and exiting", sig);
+ xlog(D_GENERAL, "Caught signal %d, un-registering and exiting", sig);
+ exit(0);