From: Richard Purdie <richard.purdie@linuxfoundation.org>
To: Patches and discussions about the oe-core layer
<openembedded-core@lists.openembedded.org>
Subject: Re: [PATCH] libnss-mdns: avoid race condition in postinst
Date: Tue, 15 Nov 2011 12:21:27 +0000 [thread overview]
Message-ID: <1321359687.26881.175.camel@ted> (raw)
In-Reply-To: <1321276012.29435.24.camel@phil-desktop>
On Mon, 2011-11-14 at 13:06 +0000, Phil Blundell wrote:
> Writing to "/tmp/nsswitch.conf" leads to a race condition if two
> copies of the postinst are running simultaneously. Fix this by
> modifying /etc/nsswitch.conf in place using sed -i. Also make the
> same change to the prerm for consistency although the race will not
> occur here in practice.
>
> Signed-off-by: Phil Blundell <philb@gnu.org>
> ---
> .../libnss-mdns/libnss-mdns_0.10.bb | 8 +++-----
> 1 files changed, 3 insertions(+), 5 deletions(-)
Merged to master, thanks.
Richard
prev parent reply other threads:[~2011-11-15 12:27 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-11-14 13:06 [PATCH] libnss-mdns: avoid race condition in postinst Phil Blundell
2011-11-15 12:21 ` Richard Purdie [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=1321359687.26881.175.camel@ted \
--to=richard.purdie@linuxfoundation.org \
--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