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

The Open Brand -- Problem Reporting and Interpretations System

Problem Report 1159 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 1159.

Report 1159 Actions

    Problem Report Number 1159
    Submitter's Classification Test Suite problem
    State Resolved
    Resolution Rejected (REJ)
    Problem Resolution ID REJ.X.0361
    Raised 1970-01-01 08:00
    Updated 2003-03-13 08:00
    Published null
    Product Standard Internationalised System Calls and Libraries Extended (UNIX 95)
    Certification Program The Open Brand certification program
    Test Suite VSU version 4.1.1
    Test Identification CAPIbase/symlink 5
    Problem Summary PG4U.00109 This request claims that the test improperly uses a relative instead of an absolute pathname.
    Problem Text

    The expected output is wrong for this testcase. The test does the
    following:

    set path1 = "../tmp/mpoint/symlink5.file"
    set path2 = "../tmp/symlink5.link"
    symlink(path1, path2)
    chdir(path2)
    getcwd(buf, sizeof(buf))
    set realone = "$TET_ROOT//CAPI/tset/CAPIbase/tmp/mpoint/symlink5.file"
    if strcmp(realone, buf)
    {
    fail
    }

    After creating the symlink and cd'ing to path2, the test gets the
    CWD by using getcwd(). If the CWD matches the absolute path of path1
    the test fails, because it is expecting to get a relative pathname.
    However, as noted on page 229 of the XSH V2 spec, getcwd() returns
    an absolute pathname not a relative pathname, so this test will always
    fail.
    Test Output
    TEST CASE: symlink

    TEST PURPOSE #5
    On a call to int symlink(const char
    *path1, const char *path2) path1 and path2 need not be
    on the same file system.
    PREP: Mount file-system read-write on ../tmp/mpoint
    PREP: Open file on the mounted file system
    PREP: Write data into this file
    TEST: symlink() creates link to files across
    filesystems.
    PREP: Save current directory location
    PREP: Make a directory on the mounted filesystem
    PREP: Create a symbolic link to this directory in
    ../tmp directory. These two directories have
    pathnames on different filesystems
    TEST: The directories across filesystems are
    successfully linked
    ERROR: symlink() did not create proper link to a
    directory on a different file system. Change of
    directory to the symbolic link failed.
    Expected: ../tmp/mpoint/symlink5.file Received: /tsuites/VSU411/CAPI/tset/CAPIb
    ase/tmp/mpoint/symlink5.file
    5 FAIL

    Review Information

    Review Type TSMA Review
    Start Date null
    Completed null
    Status Complete
    Review Recommendation No Resolution Given
    Review Response
    We recommend this request be refused.

    The submitter states the test is comparing an absolute pathname (from
    getcwd()) to a second, relative path defined as

    $TET_ROOT//CAPI/tset/CAPIbase/tmp/mpoint/symlink5.file

    We believe this second path is also an absolute path since it starts with
    the environment variable, TET_ROOT, which must be an absolute pathname
    on properly configured systems.

    We do feel the error message emitted could be improved as it prints the
    relative, rather than absolute, path, which is confusing.

    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