From: <wenzong.fan@windriver.com>
To: <openembedded-core@lists.openembedded.org>
Subject: [PATCH 0/1] rpcbind: fix init status and exit code
Date: Wed, 11 Dec 2013 04:07:05 -0500 [thread overview]
Message-ID: <cover.1386752117.git.wenzong.fan@windriver.com> (raw)
From: Wenzong Fan <wenzong.fan@windriver.com>
Currently run the '/etc/init.d/rpcbind status' on target, it only exits
with 0/1 and not any prompt messages.
The change get it prints status messages and exit with proper code.This
also allows debian service script to get rpcbind status correctly.
The following changes since commit d754ddcec78f5e264100ceda854e8412679d6866:
bitbake: process: Add timeout to select call (2013-12-10 17:55:29 +0000)
are available in the git repository at:
git://git.pokylinux.org/poky-contrib wenzong/rpcbind
http://git.pokylinux.org/cgit.cgi/poky-contrib/log/?h=wenzong/rpcbind
Wenzong Fan (1):
rpcbind: fix init status and exit code
meta/recipes-extended/rpcbind/rpcbind/init.d | 8 +++++---
1 file changed, 5 insertions(+), 3 deletions(-)
--
1.7.9.5
next reply other threads:[~2013-12-11 9:07 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-12-11 9:07 wenzong.fan [this message]
2013-12-11 9:07 ` [PATCH 1/1] rpcbind: fix init status and exit code wenzong.fan
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=cover.1386752117.git.wenzong.fan@windriver.com \
--to=wenzong.fan@windriver.com \
--cc=openembedded-core@lists.openembedded.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox