From Fedora Project Wiki

(Correct use of Template:QA/Test_Case)
No edit summary
Line 9: Line 9:
#: mkdir /nfs
#: mkdir /nfs
#: service nfs restart</pre>
#: service nfs restart</pre>
# ''Download'' connectathon testsuite.
# ''Download'' pynfs testsuite.
#: <pre>
#: <pre>
#: git clone git://linux-nfs.org/~iisaman/pynfs.git </pre>
#: git clone git://linux-nfs.org/~iisaman/pynfs.git </pre>
# From the ''client'' system, run the connectathon testsuite.
# From the ''client'' system, run the pynfs testsuite.
#: <pre>
#: <pre>
#: cd pynfs
#: cd pynfs
#: make
#: ./setup.py build_ext --inplace
#: ./runcthon --server <server IP> --serverdir /nfs</pre>
#: ./testserver.py --maketree 127.0.0.1:/nfs all</pre>


|results=
|results=

Revision as of 04:35, 1 February 2010

Description

This test case is to run pynfs test suite on a NFSv4 root


How to test

  1. You can run both NFS server and client on the same system or use different systems. First, configure the NFS server.
    cp /etc/exports /etc/exports.orig
    echo '/nfs *(rw,insecure,no_root_squash)' >/etc/exports
    mkdir /nfs
    service nfs restart
  2. Download pynfs testsuite.
    git clone git://linux-nfs.org/~iisaman/pynfs.git
  3. From the client system, run the pynfs testsuite.
    cd pynfs
    ./setup.py build_ext --inplace
    ./testserver.py --maketree 127.0.0.1:/nfs all

Expected Results

  1. Step #1 completes without error.
  2. The testsuite finishes without error; no nfs*.error files in /tmp.