Home • About Us • A-Z Index • Search * Contact Us • Register • Login • Press • Shop

The Open Brand -- Problem Reporting and Interpretations System

Problem Report 0499 Details

Help Show help | Quick Search | Submit a Test Suite Support Request | Click here to view your privileges

This page provides all information on Problem Report 0499.

Report 0499 Actions

    Problem Report Number 0499
    Submitter's Classification Specification problem
    State Resolved
    Resolution Rejected (REJ)
    Problem Resolution ID REJ.X.0118
    Raised 1995-09-19 08:00
    Updated 2003-03-13 08:00
    Published null
    Product Standard PC(NFS) server
    Certification Program The Open Brand certification program
    Test Suite PCNFS version 1.1.2
    Test Identification PCNFS.prtl/nfs/remove 6
    Problem Summary PG4R.119 The above test case is failing because our implementation supports the unlinking of directories. The unlinking of directories is an option of the VSX+XNFS test suite and must be supported via the REMO...
    Problem Text
    The above test case is failing because our implementation supports
    the unlinking of directories. The unlinking of directories is an
    option of the VSX+XNFS test suite and must be supported via the
    REMOVE operation. Since most UNIX type operating systems support
    the unlinking of directories, it would be impossible with the NFS
    version 2 protocol to determine if the user really wanted to unlink
    the direstory (via REMOVE) or was making a mistake and trying to
    remove the directory with the REMOVE operation.

    Our implementatino returns 1 (EPERM) only because the process does
    not have the proper permission to unlink the directory.

    Once again, the specification is unclear as to how unlinking of
    directories and removing of directories should be handled. If we
    return EISDIR for a REMOVE operation, many of the VSX+XNFS unlink
    tests fail. This clearly indicates that there is some sort of
    grey area in the interpretation of the specification.

    Since unlink of directories is so common place among UNIX type
    operating systems and is supported by the specification, I feel
    that the return value of EISDIR on the REMOVE operation is not
    appropriate and the requested intent of the REMOVE of a directory
    can only be intrepreted as an unlink of that directory.
    Test Output
    10|1 /tset/PCNFS.prtl/nfs/remove/T.remove 09:48:57|TC Start, scenario ref 4-1, I
    Cs {6}
    15|1 2.3 1|TCM Start
    400|1 6 1 09:48:58|IC Start
    200|1 6 09:48:58|TP Start
    520|1 6 00018470 1 1|NFSPROC_REMOVE returned incorrect status
    520|1 6 00018470 1 2|expected <21> actual <1>
    220|1 6 101 09:48:58|WARNING
    410|1 6 1 09:48:58|IC End
    80|1 0 09:48:58|TC End
    820||Remote End
    900|09:48:59|TCC End

    Review Information

    Review Type TSMA Review
    Start Date null
    Completed null
    Status Complete
    Review Recommendation No Resolution Given
    Review Response
    The test result is a WARNING and it is not necessary to obtain a waiver
    for warning results. It is recommended that this request is refused.

    Review Type SA Review
    Start Date null
    Completed null
    Status Complete
    Review Resolution Rejected (REJ)
    Review Conclusion
    This request is refused.

    Problem Reporting System Options:

     

    Back   

Contact the Certification Authority