From: Kang Kai <Kai.Kang@windriver.com>
To: <openembedded-core@lists.openembedded.org>
Subject: Re: [PATCH] avahi: restore rlimit-nproc tweak for avahi discovery
Date: Wed, 13 Jul 2016 15:32:52 +0800 [thread overview]
Message-ID: <5785EEA4.3080800@windriver.com> (raw)
In-Reply-To: <1457416218-21537-1-git-send-email-Zhixiong.Chi@windriver.com>
On 2016年03月08日 13:50, Zhixiong Chi wrote:
> Looks like we are still falling victim to:
> "chroot.c: fork() failed: Resource temporarily unavailable) = 57"
> So we restore the removal of rlimit-nproc in avahi.conf, and could
> receive return value from daemon process to start avahi-daemon.service
> successfully.
>
> The original patch is from
> <https://github.com/WindRiver-OpenSourceLabs/overc-installer>
> <commit 1ee34b64b676c79d71e1a9f2fb5dfa80d3616714>
>
> Signed-off-by: Bruce Ashfield <bruce.ashfield@windriver.com>
> Signed-off-by: Zhixiong Chi <Zhixiong.Chi@windriver.com>
> ---
> meta/recipes-connectivity/avahi/avahi.inc | 1 +
> 1 file changed, 1 insertion(+)
>
> diff --git a/meta/recipes-connectivity/avahi/avahi.inc b/meta/recipes-connectivity/avahi/avahi.inc
> index faa8ee8..65bdf6b 100644
> --- a/meta/recipes-connectivity/avahi/avahi.inc
> +++ b/meta/recipes-connectivity/avahi/avahi.inc
> @@ -63,6 +63,7 @@ LDFLAGS_append_uclinux-uclibc = " -lintl"
>
> do_configure_prepend() {
> sed 's:AM_CHECK_PYMOD:echo "no pymod" #AM_CHECK_PYMOD:g' -i ${S}/configure.ac
> + sed -i "s/^.*rlimit\-nproc=.*/# rlimit-nproc=3/" ${S}/avahi-daemon/avahi-daemon.conf
> }
>
>
Any comment on this patch?
Thanks.
--
Regards,
Neil | Kai Kang
prev parent reply other threads:[~2016-07-13 7:32 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-03-08 5:50 [PATCH] avahi: restore rlimit-nproc tweak for avahi discovery Zhixiong Chi
2016-07-13 7:32 ` Kang Kai [this message]
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=5785EEA4.3080800@windriver.com \
--to=kai.kang@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