资源说明:The "Connectathon NFS tests", as published on www.connectathon.org for the Connectathon 2004 event. The test directories contain programs that can be used to test an implementation of the NFS Protocol. The tests run on a UNIX client and test server and client functions. See the file README in this repository for more information.
# # @(#)README 1.18 2003/12/30 Connectathon Testsuite # NFS and Connectathon are trademarks of Sun Microsystems, Inc. Introduction to the Connectathon NFS Testsuites --------------------------------------------- These directories contain programs that can be used to test an implementation of the NFS Protocol. The tests run on a UNIX client and test server and client functions. (See READWIN.txt for information about running on DOS and Windows.) The tests are divided into three groups: basic - basic file system operations tests general - general file system tests special - tests that poke certain common problem areas lock - tests that exercise network locking This README is divided into five sections. The first section is the introduction, which you are reading now. That is followed by a description of what you have to do before you run the testsuites on your machine. Then comes a description of how the testsuites are run in general followed by a description of how they are used at Connectathon. The last section describes what each test does in detail. This testsuite should run on both BSD and System V based systems. The System V Release 3 port of the Connectathon Testsuite is provided courtesy of the Lachman Technology, Incorporated, 1901 N. Naper Blvd., Naperville, IL. 60563. Preparing to run the Testsuites ------------------------------- To prepare to run the testsuites on your machine, change directories to the highest level testsuite directory (it should be the same one that contains this README file), edit tests.init according to the platform you are on, and type "make" to compile the test programs. If you are not sure you are in the correct directory, type "ls -CF" and you should see the following files and directories: Makefile basic/ lock/ tests.h README domount.c runtests tests.init READWIN.txt general/ server tools/ Testitems getopt.c special/ unixdos.h The "server" script uses "getopt". A source file of a public-domain version of "getopt" is included in the directory. The Makefile will compile it for you. The tests are configured according to parameters found in the script, tests.init. It contains various definitions for commands and parameters used by the various Makefiles and shell scripts. This file should be checked and then perhaps modified to correctly match your system. In particular, the values of "MOUNTCMD", "UMOUNTCMD", "PATH", "CFLAGS", and "LIBS" should be checked and set correctly. There are several sets of suggested values which may be used as possible starting places. Two special targets are included in the Makefiles: copy and dist. The command, "make copy DESTDIR="path"", where "path" is the absolute name of a directory, will cause the compiled tests to be copied to "path". The command, "make dist DESTDIR="path"", where "path" is the absolute name of a directory, will copy the test sources to "path". DESTDIR must be specified on the make command line when making either of these targets. Modifications may be required so the programs compile on your machine. If that is so, we would like to know what they are so that we can incorporate them into our distribution. When defaults are used, the test programs expect the directory, /server, to exist on the server. The test driver will use the directory /mnt/'server_name' on the client, creating it first if necessary (where 'server_name' is the name of the server you are testing against). These defaults can be overridden at run time. Directions for doing this are contained in the next section. How to run the Testsuites ------------------------- There are two ways to run the tests: use the server shell script or mount, run the tests yourself, and unmount. We recommend you use the server script to run the tests. The server script: The server script executes one or more of the test sets depending on what option is given (see below). It is set up to mount, run tests using the runtests program, and unmount. It will attempt to unmount anything mounted on the mount point before attempting to mount the server file system. If a test fails, the run is aborted and the file system is left mounted to assist in troubleshooting the failure. The server script uses the domount program to mount and unmount the test file systems. Since mount can only be executed by root, domount must have root permission. The Makefile will attempt to setuid the domount program to root. The server script can be run as a nonprivileged user. Alternately, you may login as root before you run server. server [-a|-b|-g|-s|-l] [-f|-t] [-n] [-o mnt_options] [-p server_path] [-m mntpoint] [-N numpasses] server_name -a|-b|-g|-s|-l - will be passed on to the runtests scripts. This argument is optional. The default is read from the initialization file, tests.init. The variable, TEST, contains this argument. This argument selects which tests to run: -a run basic, general, special, and lock tests -b run basic tests only -g run general tests only -s run special tests only -l run lock tests only -f|-t - will be passed on to the runtests scripts. This argument is optional. The default is read from the initialization file, tests.init. The variable, TESTARG, contains this argument. This argument selects how the basic tests are to be run: -f a quick functionality test -t extended test mode with timings -n - Don't perform the mkdir and rmdir operations to create and destroy the test directory. -o mnt_options - will be passed on to the mount command. This argument is optional. The default is read from the initialization file, tests.init. The variable, MNTOPTIONS, contains this argument. -p server_path - specifies a directory on the server to mount. This argument is optional. The default is read from the initialization file, tests.init. The variable, SERVPATH, contains this argument. -m mntpoint - specifies a mount point on your client. This argument is optional. The default is read from the initialization file, tests.init. The variable, MNTPOINT, contains this argument. -N numpasses - will be passed to the runtests script. This argument is optional. It specifies the number of times to run through the tests. server_name - the server you want to exercise. This is the only required argument. The test programs create a sub-directory in the mntpoint directory with the name, 'hostname'.test, (where 'hostname' is the name of the machine on which you run the tests). This name can not be overridden if you use the server script although it can be if you use runtests directly. Example: (the client machine is eddie) eddie% server -o hard,intr,rw slartibartfarst Start tests on path /mnt.slartibartfast/eddie.test [y/n]? y
本源码包内暂不包含可直接显示的源代码文件,请下载源码包。