Hi Omar, Please find my comments adhered:
On Mon, 2007-10-22 at 13:30 +0530, Mohammed Omar wrote: > hi subrata, > I found some abnormalities in LTP > > > ltp-network: tesscripts/networktests.sh > --------------------------------------- > 1.I found always nfsx-linux fails for me. when I need to search for it > i need to search fsx-linux( as u mentioned in ur last mail).And there I > need to run fsx.sh not fsx-linix. Here nfsx-linux is the test tag <name by which we will know the test case>, whereas the actually binary that gets executed is different (IN most of cases, the Tag name and the binary names are the same, unfortunately not so here). Now whatever follows the tag name is passed on to the command line for execution. If you see properly, you will find that fsx.sh is being exported lots of variables, which it will use inside the script and will ultimately call fsx-linux binary from the script. Please have a look at: ltp/testcases/network/nfs/fsx-linux/fsx.sh for exact execution sequence. > 2.When ltpnetwork.log reports ftp fail.I searched for ftp in source > tree, i found at two places /testcases/network/stress/ftp > and /testcases/network/tcp_cmds/ftp I am not sure which one failed. I can see that both are directories and there are no specific binary(s) as ftp, so, definitely again, it should be some command-file where the tag is ftp and the command (actuall binary to execute) should be something else. So, you can debug the same. > 3. ftp under tcp_cmds contain ftp01,02,03,04 etc,. When I ran each > at a time, they fails by saying that some thing is not exported.Once you > export that it again fails by saying that another Variable has to be > exported.Like this it will go on ask for some four or five varialbes, > Same thing for nfs testcases.My suggestion is Can't we have "asking > mechanism" once you run it manually. Practically/actually you should have done the network setup properly (this requires exporting lot of variables before you actually invoke the tests) rather than exporting during MANUAL run. Or, you can put all your exports in a script and do .script to make those available before your manual run. > 4. ftp testcases are searching for /etc/vsftpd.conf , which is > implemented as /etc/vsftpd/vsftpd.conf in fedora. Here testcase should > be generic. If thatś the case, you can submit me a patch for the same to generalize that (all) test case(s) for any distro(s). You can refer to: ltp/testcases/kdump/master for generalize-distro-how-to. > > > ltp-stress: testscripts/ltpstress.sh > ------------------------------------ > 1. ltpstress search for portmap domain which is implemented differently > in fedora( i need to check). Portmap package is not available in fedora. Here also you can generalize the same and give me the solution as per: ltp/testcases/kdump/master > > > These are only findings, I need to explore more, I thought if I bring it > to everyones knowledge,I may get some sort of help and suggestions. > > --thanks > omar --Thanks-- Subrata > > > ------------------------------------------------------------------------- > This SF.net email is sponsored by: Splunk Inc. > Still grepping through log files to find problems? Stop. > Now Search log events and configuration files using AJAX and a browser. > Download your FREE copy of Splunk now >> http://get.splunk.com/ > _______________________________________________ > Ltp-list mailing list > [email protected] > https://lists.sourceforge.net/lists/listinfo/ltp-list ------------------------------------------------------------------------- This SF.net email is sponsored by: Splunk Inc. Still grepping through log files to find problems? Stop. Now Search log events and configuration files using AJAX and a browser. Download your FREE copy of Splunk now >> http://get.splunk.com/ _______________________________________________ Ltp-list mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/ltp-list
