Chen Qi ab4f1b220f 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 <Qi.Chen@windriver.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>		2014-09-03 11:09:06 +01:00
..
rpcbind	rpcbind: avoid entering failed status after stopping daemon	2014-09-03 11:09:06 +01:00
rpcbind_0.2.1.bb	rpcbind: Make user's home directory /	2014-09-03 11:09:03 +01:00