On Jan 8, 2010, at 11:56 AM, Jeff Layton wrote:
On Fri, 8 Jan 2010 11:49:16 -0500
Chuck Lever <chuck.lever@xxxxxxxxxx> 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.
statd/sm-notify are supposed to be smart enough to send reboot
notifications once per reboot anyway. But it can't hurt to enforce it
here.
+}
+
+# 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@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
--
Jeff Layton <jlayton@xxxxxxxxxx>
--
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@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
