From: sumitbd@linsyssoft.com
To: ltp-list@lists.sourceforge.net
Subject: [LTP] [PATCH 2/3] nfs02: testcases/network/nfs/nfs02/nfs02 script - bug fixing
Date: Sun, 11 Jul 2010 19:04:28 +0530 [thread overview]
Message-ID: <1278855268.8660.44.camel@sumit> (raw)
Hi,
Testcase "nfs02" fails with following message
"Test Failed: Removal of write permissions not honored on ascii.sm"
This is because ascii.sm has a rwx file permission for others when It
got installed. The script first tried to remove only write permission
for others and then it tests it with the r-- permission so test get
fails as it has r-x permission for others.
This is fixed with following patch.
Index: ltp-full-20100630/testcases/network/nfs/nfs02/nfs02
===================================================================
--- ltp-full-20100630.orig/testcases/network/nfs/nfs02/nfs02
+++ ltp-full-20100630/testcases/network/nfs/nfs02/nfs02
@@ -179,7 +179,7 @@ do_test3()
{
$trace_logic
echo "do_test3 $TC "
- chmod a-w $TCtmp/ascii.sm &
+ chmod a-wx $TCtmp/ascii.sm &
wait $!
ls -l $TCtmp/ascii.sm | grep "r--"
[ $? -eq 0 ] || end_testcase "Removal of write permissions not
honored on ascii.sm"
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:58 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-07-11 13:34 sumitbd [this message]
2010-07-11 14:20 ` [LTP] [PATCH 2/3] nfs02: testcases/network/nfs/nfs02/nfs02 script - bug fixing 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=1278855268.8660.44.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 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.