]> code.ossystems Code Review - openembedded-core.git/commit
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 09:24:21 +0000 (10:24 +0100)
commit1bfc6a45e7ba81d3537ea3ae8b176f5a9c206eaa
tree03c172f76437ff9d158dc8db18c5883bf356e279
parent020065d3c57ccdc86c47cd0fc288071cdd194bbc
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);
}

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