readme

早期freebsd实现

test1: File and Directory Creation Test

This program creates the test directory (mkdir)  on the client and changes 
directories (chdir) to it,  unless the -n flag is used in which case it simply 
changes directories to the test directory.  Then it builds a directory tree  
N levels deep, where each directory (including the test directory) has M 
files and P directories (creat, close, chdir, and mkdir).  For the -f 
option N = 2, M = 2,  and P = 2 so a total of six files and six directories 
are created.  For other options N = 5, M = 5, and P = 2.  The files that are 
created are given names that begin with "file." and directories with names 
that begin with "dir.".



test2: File and directory removal test

This program changes directory to the test directory (chdir and/or mkdir) and 
removes the directory tree (unlink, chdir,  and rmdir) that was just created 
by test1.  The number of levels, files, and directories,  and the name pre-
fixes, are the same as in test1.

This routine will not remove a file or directory that was not created by test1 
and will fail if it finds one.  It determines this by looking at the prefix on 
the name of the object it's trying to remove.



test3: Lookups across mount point

This program changes directory to the test directory (chdir and/or mkdir) and 
gets the file status of the working directory (getwd and stat).    


test4: setattr, getattr, and lookup

This program changes directory to the test directory (chdir and/or mkdir) and 
creates ten files (creat).    Then the permissions are changed (chmod) and the 
file status is retrieved (stat) twice for each file. 


test4a:  getattr, and lookup

This test exists but is not called as part of the testsuite.  You can edit
runtests in the basic directory so this test is called.

This program changes directory to the test directory (chdir and/or mkdir) and 
creates ten files (creat).    Then the file status is retrieved (stat) for 
each file. 



test5: read and write
	         
This program changes directory to the test directory (chdir and/or mkdir) and 
then: 

1) Creates a file (creat) 
2) Gets status of file (fstat)
3) Checks size of file
4) Writes 1048576 bytes into the file (write) in 8192 byte buffers.  
5) Closes file (close)
6) Gets status of file (stat)
7) Checks the size of the file

Then the file is opened (open) and read (read) in 8192 byte buffers.  It's 
contents are compared with what was written.  The file is then closed (close).

Then the file is then re-opened (open) and re-read (read) before it is removed 
(unlink).

test5a: write

This test exists but is not called as part of the testsuite.  You can edit
runtests in the basic directory so this test is called.

This program changes directory to the test directory (chdir and/or mkdir) and 
then: 

1) Creates a file (creat) 
2) Gets status of file (fstat)
3) Checks size of file
4) Writes 1048576 bytes into the file (write) in 8192 byte buffers.  
5) Closes file (close)
6) Gets status of file (stat)
7) Checks the size of the file


test5b: read

This test exists but is not called as part of the testsuite.  You can edit
runtests in the basic directory so this test is called.

The file created in test5a is opened (open) and read (read) in 8192 byte 
buffers.  It's contents are compared with what was written.  The file is 
then closed (close) and removed (unlink).



test6: readdir

This program changes directory to the test directory (chdir and/or mkdir) and 
creates 200 files (creat).  The current directory is opened (opendir), the 
beginning is found (rewinddir), and the directory is read (readdir) in a loop 
until the end is found.  Errors flagged are:

1) No entry for "."
2) No entry for ".."
3) Duplicate entry
4) Filename that doesn't begin with "file."
5) The suffix of the filename is out of range
6) An entry is returned for an unlinked file. (This error can only be
   found when the test is run with an option other than -f.   For other
   options the readdir loop is done multiple times and a file is unlinked
   each time).  

The directory is then closed (closedir) and the files that were created are 
removed (unlink). 



test7: link and rename

This program changes directory to the test directory (chdir and/or mkdir) and 
creates ten files.  For each of these files, the file is renamed (rename) and 
file statistics are retrieved (stat) for both the new and old names.  Errors 
that are flagged are:

1) Old file still exists
2) New file doesn't exist (can't stat)
3) The new file's number of links doesn't equal one

Then an attempt is made to link the new file to it's old name (link) and file 
stats are again retrieved (stat).  An error is flagged if:

1) Can't link
2) Stats on new file can't be retrieved after link  
3) The new file's number of links doesn't equal two
4) Stats on old file can't be retrieved after link  
5) The old file's number of links doesn't equal two
 
Then the new file is removed (unlink) and file stats are retrieved for the old 
file (stat).  An error is flagged if:

1) Stats on old file can't be retrieved after unlink
2) The old file's number of links doesn't equal one

Any files that remain at the end of the test are removed (unlink).

test7a: rename

This test exists but is not called as part of the testsuite.  You can edit
runtests in the basic directory so this test is called.

This program changes directory to the test directory (chdir and/or mkdir) and 
creates ten files.  For each of these files, the file is renamed (rename) and 
file statistics are retrieved (stat) for both the new and old names.  Errors 
that are flagged are:

1) Old file still exists
2) New file doesn't exist (can't stat)
3) The new file's number of links doesn't equal one

Any files that remain at the end of the test are removed (unlink).

test7b: link

This test exists but is not called as part of the testsuite.  You can edit
runtests in the basic directory so this test is called.

This program changes directory to the test directory (chdir and/or mkdir) and 
creates ten files.  A link (link) is done for each of these files, and file 
stats are retrieved for the old and new files (stat).  An error is flagged 
if:

1) Can't link
2) Stats on either file can't be retrieved after link
3) The either file's number of links doesn't equal two

This is followed by an unlink (unlink) of the new file.  An error is 
flagged if:

1) Stats on the old file can't be retrieved after unlink
2) The old file's number of links doesn't equal one

Any files that remain at the end of the test are removed (unlink).



test8: symlink and readlink

NOTE:   Not all operating systems support symlink and readlink.  If the
	errno EOPNOTSUPP is returned during test8, the test will be
	counted as passing.  For clients not supporting S_IFLNK, the
	test will not be attempted.

This program changes directory to the test directory (chdir and/or mkdir) and 
makes 10 symlinks (symlink).  It reads (readlink), and gets statistics for 
(lstat), each, and then removes them (unlink).  Errors flagged are:

1) Unsupported function
2) Can't get statistics (lstat failed)
3) The mode in the stats is not symlink
4) The value of the symlink is incorrect (returned from readlink)
5) The linkname is wrong
6) The unlink failed



test9: statfs

This program changes directory to the test directory (chdir and/or mkdir) and 
gets the file system status on the current directory (statfs).




- GENERAL:  General tests to look at server loading.

Runs a small compile, Tbl, Nroff and a Large Compile. Four simultaneous
large compiles are also run.




- SPECIAL:  Information specific to the special tests

The special directory is set up to test special problems that have
come up in the past.  These tests are meant to be advisory, ...
things to watch out for.  It is not required that you "pass" these
tests but we suggest you give them a try.

The tests try to:

      check for proper open/unlink operation
      check for proper open/chmod 0 operation
      check for lost reply on non-idempotent requests
      test exclusive create
      test negative seek
      test rename




- MISC:

'Testitems' is a list of NFS functionality that can be used for reference.

Programs in 'tools' are provided for your use as you see fit.  Please
feel free to add to this (or any other) directory!  If you do, please
make sure that Cathe Ray (sun!cathe or [e-mail]) at Sun gets a copy 
so we can add it to the master test distribution.