From: wenzong fan <wenzong.fan@windriver.com>
To: <openembedded-core@lists.openembedded.org>
Subject: Re: [PATCH v3] rpcbind: handle rpcbind options
Date: Fri, 16 Oct 2015 14:36:04 +0800 [thread overview]
Message-ID: <56209AD4.3090809@windriver.com> (raw)
In-Reply-To: <1436941198-24451-1-git-send-email-wenzong.fan@windriver.com>
Ping again ...
Thanks
Wenzong
On 07/15/2015 02:19 PM, wenzong.fan@windriver.com wrote:
> From: Li Wang <li.wang@windriver.com>
>
> While runing:
>
> $ systemctl restart rpcbind
> $ systemctl status rpcbind
>
> There are errors like below:
> rpcbind[1722]: Cannot open '/tmp/rpcbind.xdr' file for reading, \
> errno 2 (No such file or directory)
> rpcbind[1722]: Cannot open '/tmp/portmap.xdr' file for reading, \
> errno 2 (No such file or directory)
>
> Don't pass -w to rpcbind on boot up, since the files won't be there
> to be read, the patch refers to:
> https://bugs.launchpad.net/ubuntu/+source/rpcbind/+bug/835833
>
> Signed-off-by: Li Wang <li.wang@windriver.com>
> Signed-off-by: Wenzong Fan <wenzong.fan@windriver.com>
> ---
> meta/recipes-extended/rpcbind/rpcbind/rpcbind.service | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/meta/recipes-extended/rpcbind/rpcbind/rpcbind.service b/meta/recipes-extended/rpcbind/rpcbind/rpcbind.service
> index b3ae254..9cdade4 100644
> --- a/meta/recipes-extended/rpcbind/rpcbind/rpcbind.service
> +++ b/meta/recipes-extended/rpcbind/rpcbind/rpcbind.service
> @@ -5,7 +5,7 @@ Requires=rpcbind.socket
> [Service]
> Type=forking
> EnvironmentFile=-@SYSCONFDIR@/rpcbind.conf
> -ExecStart=@SBINDIR@/rpcbind -w $RPCBIND_OPTS
> +ExecStart=@SBINDIR@/rpcbind $RPCBIND_OPTS
> SuccessExitStatus=2
>
> [Install]
>
next prev parent reply other threads:[~2015-10-16 6:36 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-07-15 6:19 [PATCH v3] rpcbind: handle rpcbind options wenzong.fan
2015-07-24 8:04 ` wenzong fan
2015-10-16 6:36 ` wenzong fan [this message]
2015-10-26 17:41 ` Burton, Ross
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=56209AD4.3090809@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.