Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
To: buildroot@busybox.net
Subject: [Buildroot] [git commit] nfs-utils: Bump version
Date: Mon, 13 Jul 2015 13:27:27 +0200	[thread overview]
Message-ID: <20150713132727.36186916@free-electrons.com> (raw)
In-Reply-To: <20150713111001.GQ2451@tarshish>

Dear Baruch Siach,

On Mon, 13 Jul 2015 14:10:01 +0300, Baruch Siach wrote:
> Hi Thomas,
> 
> On Mon, Jul 13, 2015 at 12:54:42PM +0200, Thomas Petazzoni wrote:
> > [Thomas: add patch to fix rpc.statd foreground/daemon mode backported
> > from upstream, and fix the S60nfs init script to not use the -F option
> > of rpc.statd.]
> 
> [snip]
> 
> > diff --git a/package/nfs-utils/S60nfs b/package/nfs-utils/S60nfs
> > index 91410ee..5e2a2c9 100755
> > --- a/package/nfs-utils/S60nfs
> > +++ b/package/nfs-utils/S60nfs
> > @@ -21,7 +21,6 @@ start() {
> >  
> >  	echo -n "Starting NFS services: "
> >  	/usr/sbin/exportfs -r
> > -	rpc.statd
> 
> rpc.statd invocation removed entirely. Is this intended?

Wow, this puzzled me for a bit. But here is what happened. Before the
patch, the code looked like this:

	echo -n "Starting NFS statd: "
	rpc.statd
	touch /var/lock/subsys/nfslock
	echo "done"

	echo -n "Starting NFS services: "
	/usr/sbin/exportfs -r
	rpc.statd
	echo "done"

So the first invocation to rpc.statd is kept, but not the second one.
So rpc.statd is still started, but only once.

Maxime, can you confirm this is OK ?

Thomas
-- 
Thomas Petazzoni, CTO, Free Electrons
Embedded Linux, Kernel and Android engineering
http://free-electrons.com

  parent reply	other threads:[~2015-07-13 11:27 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-07-13 10:54 [Buildroot] [git commit] nfs-utils: Bump version Thomas Petazzoni
2015-07-13 11:10 ` Baruch Siach
2015-07-13 11:27   ` Maxime Hadjinlian
2015-07-13 11:27   ` Thomas Petazzoni [this message]
2015-07-13 11:34     ` Baruch Siach
  -- strict thread matches above, loose matches on Subject: below --
2015-10-04 16:49 Thomas Petazzoni

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=20150713132727.36186916@free-electrons.com \
    --to=thomas.petazzoni@free-electrons.com \
    --cc=buildroot@busybox.net \
    /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