From: Jeff Layton <jlayton@redhat.com>
To: Chuck Lever <chuck.lever@oracle.com>
Cc: steved@redhat.com, bfields@fieldses.org, linux-nfs@vger.kernel.org
Subject: Re: [PATCH 4/4] nfs-utils: add initial tests for statd that run via "make check"
Date: Fri, 8 Jan 2010 11:56:51 -0500 [thread overview]
Message-ID: <20100108115651.7a84a3c5@tlielax.poochiereds.net> (raw)
In-Reply-To: <70DEDD50-4AC5-4377-B5FA-A1FBCD92EBF3@oracle.com>
On Fri, 8 Jan 2010 11:49:16 -0500
Chuck Lever <chuck.lever@oracle.com> wrote:
>
> Basically what this tells me is that you can't runs these tests at all
> if your development tree lives on an NFSv2/3 mount point.
>
I don't think the test I have so far will do any fcntl locking, so that
one would probably work. No guarantees on any that are added later though.
It's probably best to assume that doing so would be problematic.
> > + fi
> > + $srcdir/../utils/statd/statd --no-notify
>
> Is --no-notify really needed? I guess that's just a safety net.
>
Yeah. On the off chance that someone has monitored hosts in the db
after shutting down statd, I don't think we want to start spraying
notifications when we start the test.
> > +}
> > +
> > +# shut down statd
> > +kill_statd() {
> > + kill `cat /var/run/rpc.statd.pid`
> > +}
> > --
> > 1.6.5.2
>
> --
> Chuck Lever
> chuck[dot]lever[at]oracle[dot]com
>
>
>
> --
> To unsubscribe from this list: send the line "unsubscribe linux-nfs" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at http://vger.kernel.org/majordomo-info.html
>
--
Jeff Layton <jlayton@redhat.com>
next prev parent reply other threads:[~2010-01-08 16:56 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-01-08 14:55 [PATCH 0/4] nfs-utils: add testing infrastructure to nfs-utils (try #6) Jeff Layton
2010-01-08 14:56 ` [PATCH 1/4] nfs-utils: make private cookie to hex conversion a library routine Jeff Layton
2010-01-08 14:56 ` [PATCH 2/4] nfs-utils: introduce new statd testing simulator Jeff Layton
2010-01-08 14:56 ` [PATCH 3/4] nfs-utils: add statdb_dump utility Jeff Layton
2010-01-08 14:56 ` [PATCH 4/4] nfs-utils: add initial tests for statd that run via "make check" Jeff Layton
2010-01-08 16:49 ` Chuck Lever
2010-01-08 16:56 ` Jeff Layton [this message]
[not found] ` <20100108115651.7a84a3c5-9yPaYZwiELC+kQycOl6kW4xkIHaj4LzF@public.gmane.org>
2010-01-08 18:21 ` Chuck Lever
2010-01-08 16:59 ` J. Bruce Fields
2010-01-12 12:25 ` [PATCH 0/4] nfs-utils: add testing infrastructure to nfs-utils (try #6) Steve Dickson
-- strict thread matches above, loose matches on Subject: below --
2010-01-06 15:20 [PATCH 0/4] nfs-utils: add testing infrastructure to nfs-utils (try #5) Jeff Layton
2010-01-06 15:20 ` [PATCH 4/4] nfs-utils: add initial tests for statd that run via "make check" Jeff Layton
2010-01-06 12:53 [PATCH 0/4] nfs-utils: add testing infrastructure to nfs-utils (try #4) Jeff Layton
2010-01-06 12:53 ` [PATCH 4/4] nfs-utils: add initial tests for statd that run via "make check" Jeff Layton
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=20100108115651.7a84a3c5@tlielax.poochiereds.net \
--to=jlayton@redhat.com \
--cc=bfields@fieldses.org \
--cc=chuck.lever@oracle.com \
--cc=linux-nfs@vger.kernel.org \
--cc=steved@redhat.com \
/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.