From ab4f1b220f2da29c877be90eee5e3ac09e34c060 Mon Sep 17 00:00:00 2001 From: Chen Qi Date: Wed, 3 Sep 2014 15:09:11 +0800 Subject: rpcbind: avoid entering failed status after stopping daemon Exiting with '2' is actually expected with rpcbind, because it catches SIGTERM and exits with '2' explicitly. The related code is as follows. (void) signal(SIGTERM, terminate); /* * Catch the signal and die */ static void terminate(int dummy /*__unused*/) { close(rpcbindlockfd); unlink(_PATH_RPCBINDSOCK); unlink(RPCBINDDLOCK); syslog(LOG_ERR, "rpcbind terminating on signal. Restart with \"rpcbind -w\""); write_warmstart(); /* Dump yourself */ exit(2); } (From OE-Core rev: 1bfc6a45e7ba81d3537ea3ae8b176f5a9c206eaa) Signed-off-by: Chen Qi Signed-off-by: Richard Purdie --- meta/recipes-extended/rpcbind/rpcbind/rpcbind.service | 1 + 1 file changed, 1 insertion(+) (limited to 'meta/recipes-extended/rpcbind') diff --git a/meta/recipes-extended/rpcbind/rpcbind/rpcbind.service b/meta/recipes-extended/rpcbind/rpcbind/rpcbind.service index 4de28d4ae1..33ee268441 100644 --- a/meta/recipes-extended/rpcbind/rpcbind/rpcbind.service +++ b/meta/recipes-extended/rpcbind/rpcbind/rpcbind.service @@ -9,6 +9,7 @@ Type=forking EnvironmentFile=-@SYSCONFDIR@/rpcbind.conf ExecStart=@SBINDIR@/rpcbind -w $RPCBIND_OPTS Restart=always +SuccessExitStatus=2 [Install] WantedBy=multi-user.target -- cgit v1.2.3-54-g00ecf