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

The Open Brand -- Problem Reporting and Interpretations System

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

Report 1584 Actions

    Problem Report Number 1584
    Submitter's Classification Specification problem
    State Resolved
    Resolution Permanent Interpretation (PIN)
    Problem Resolution ID PIN.X.0141
    Raised 1995-09-04 08:00
    Updated 2003-03-13 08:00
    Published 1995-11-08 08:00
    Product Standard Internationalised System Calls and Libraries Extended (UNIX 95)
    Certification Program The Open Brand certification program
    Test Suite VSU version 4.1.0
    Test Identification CAPI.os/procenv/setrlimit 15
    Specification System Interfaces and Libraries Issue 4 Version 2
    Location in Spec See Problem Text
    Problem Summary PIN4U.00007 RLIMIT_FSIZE = 0 should not prevent creation of a file.
    Problem Text
    The XoTGbase working group has passed a resolution 1170/92
    indicating that the change from historical behavior (which was to
    create a zero length file) was not intentional, and that such
    behavior is conforming.

    The text of 1170/92 is as follows:

    [Request text starts:]

    The getrlimit() page states that RLIMIT_FSIZE = 0 prevents
    creation of a file (SVID3 says this also).

    Looking at BSD , SVR4 and Solaris 2.4 this does not seem
    to be the practise in general.

    1. Was this intentional to change from existing behavior of the
    above systems?

    2. If so, what is the required behavior for an error for the
    open() and creat() functions? There is no applicable errno for
    this case. To overload an existing errno, such as EFBIG would not be
    appropriate.

    [text ends.]

    X/OPEN RESOLUTION:

    The change to historical behaviour was not intentional.
    The behaviour to create a zero length file is permitted. It is
    recommended that a future revision clarify the requirements in
    this area.
    Test Output
    TEST CASE: setrlimit

    TEST PURPOSE #15
    If the implementation does not inhibit enforcement of
    limits for the resource RLIMIT_FSIZE:
    When the limit for the resource RLIMIT_FSIZE is set to
    0 by a call to int setrlimit(int resource, const
    struct rlimit *rlp) the calling process shall be
    prevented from creating files.
    PREP: Fork a child process
    PREP: Obtain the current limits
    PREP: child: Set the limits for RLIMIT_FSIZE to 0
    TEST: Process is prevented from creating a file
    ERROR: The process could open a file even though the
    RLIMIT_FSIZE was 0
    15 FAIL

    Review Information

    Review Type TSMA Review
    Start Date null
    Completed null
    Status Complete
    Review Recommendation No Resolution Given
    Review Response
    A permanent interpretation is recommended.

    Review Type SA Review
    Start Date null
    Completed null
    Status Complete
    Review Resolution Permanent Interpretation (PIN)
    Review Conclusion
    A Permanent Interpretation is granted.

    Problem Reporting System Options:

     

    Back   

Contact the Certification Authority