From: sumitbd@linsyssoft.com
To: ltp-list@lists.sourceforge.net
Subject: [LTP] [PATCH 3/3] runtest/nfs: TCbin path not exported for few tests
Date: Sun, 11 Jul 2010 19:08:18 +0530 [thread overview]
Message-ID: <1278855498.8660.48.camel@sumit> (raw)
Hi,
While running networktest for nfs; nfsstress & nfsstat01 test gets
fail. Because TCbin is not exported with required path. Following
patch fixed the above problem.
Index: ltp-full-20100630/runtest/nfs
===================================================================
--- ltp-full-20100630.orig/runtest/nfs
+++ ltp-full-20100630/runtest/nfs
@@ -6,10 +6,10 @@ nfs01 export VERSION SOCKET_TYPE; TCbin=
nfs02 export VERSION SOCKET_TYPE; TCbin=$LTPROOT/testcases/bin nfs02
nfs03 export VERSION SOCKET_TYPE; TCbin=$LTPROOT/testcases/bin nfs03
nfs04 export VERSION SOCKET_TYPE; TCbin=$LTPROOT/testcases/bin nfs04
-nfslock01 export VERSION; nfslock01
+nfslock01 export VERSION; TCbin=$LTPROOT/testcases/bin nfslock01
# This will run 1 thread on 20 directories with 50 files in each.
-nfsstress export VERSION SOCKET_TYPE; nfsstress 20 50 1
+nfsstress export VERSION SOCKET_TYPE; TCbin=$LTPROOT/testcases/bin
nfsstress 20 50 1
nfsstat01 export VERSION; TCbin=$LTPROOT/testcases/bin nfsstat01
nfsx-linux export VERSION SOCKET_TYPE; TCbin=$LTPROOT/testcases/bin
fsx.sh
Thanks & Regards
Sumit Dhoot
System Administrator
Linsyssoft Technologies Pvt. Ltd.
sumitbd@linsyssoft.com
------------------------------------------------------------------------------
This SF.net email is sponsored by Sprint
What will you do first with EVO, the first 4G phone?
Visit sprint.com/first -- http://p.sf.net/sfu/sprint-com-first
_______________________________________________
Ltp-list mailing list
Ltp-list@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/ltp-list
next reply other threads:[~2010-07-11 13:45 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-07-11 13:38 sumitbd [this message]
2010-07-11 14:22 ` [LTP] [PATCH 3/3] runtest/nfs: TCbin path not exported for few tests Sumit Dhoot
2010-07-11 17:05 ` Garrett Cooper
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=1278855498.8660.48.camel@sumit \
--to=sumitbd@linsyssoft.com \
--cc=ltp-list@lists.sourceforge.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