rpcbind: avoid entering failed status after stopping daemon
authorChen Qi <Qi.Chen@windriver.com>
Wed, 3 Sep 2014 07:09:11 +0000 (15:09 +0800)
committerRichard Purdie <richard.purdie@linuxfoundation.org>
Wed, 3 Sep 2014 10:09:06 +0000 (11:09 +0100)
commitf2323460d57d70976f2d27ea44c8bd8733567b02
tree18bbbdd3721bdd2d9108fe2b0df81ae50c59712f
parent9fc78d9171f3bf86edbea28034cc0ca423dbce38
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>
meta/recipes-extended/rpcbind/rpcbind/rpcbind.service