HomeAbout Us A-Z IndexSearch * Contact Us Register LoginPress Shop

The Open Brand -- Problem Reporting and Interpretations System


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


Report 0701 Actions


    Problem Report Number 0701
    Submitter's Classification Specification problem
    State Resolved
    Resolution Permanent Interpretation (PIN)
    Problem Resolution ID PIN.X.0094
    Raised 1970-01-01 08:00
    Updated 2003-03-13 08:00
    Published 1997-07-07 08:00
    Product Standard Commands and Utilities V2 (UNIX 95)
    Certification Program The Open Brand certification program
    Test Suite VSC version 4.1.4
    Test Identification POSIX.cmd/mkfifo/mkfifo 19, 27-32, 33
    Specification Commands and Utilities Issue 4 Version 2
    Location in Spec See Problem Text
    Problem Summary PIN4C.00020 The tests expect that the mkfifo -m command will be affected by the current setting of umask. This is not necessary.
    Problem Text
    The tests expect that the mkfifo -m command will be affected
    by the current setting of umask. This is not necessary.

    This following incorrectly documents historical practice of the
    mkfifo command:

    POSIX.2 sections 4.42.2 and 4.42.3 describe the behavior of
    the -m option.
    4.42.2 (2) The value of the bitwise inclusive OR of the
    S_IRUSR, S_IWUSR, S_IRGRP, S_IWGRP, S_IROTH, and S_IWOTH
    is used as the mode argument. (If the -m option is specified,
    the mode option-argument overrides this default.)

    4.42.3 -m mode
    Set the file permission bits of the newly created directory
    to the specified mode value.

    The VSC4 test suite expects that the mkfifo command will be
    affected by the current setting of umask.

    The mode of the new fifo when the -m option is used
    should be set to the explict value specified by the mode
    argument to -m.

    The correct behaviour for mkdir is described in POSIX.2b
    draft.11 section 4.41.2 and 4.41.3 on page 67. For
    consistency with mkdir, the behavior of mkfifo and mkdir
    with the -m option should be considered in parallel.

    Our implementation conforms to the draft POSIX.2b standard which
    mandated the historical behaviour in this area. Since this
    area of the specification is subject to change, we request a
    temporary interpretation allowing historical practice.

    Test Output
    200|1 1 06:59:55|TP Start
    520|1 1 5308422 1 1|Assertion #19 (A): Check -m mode in general with nonzero umask
    520|1 1 5308422 1 1|Command failed: 'expr "Xprw-rw-rw-" : 'Xprw[A-Z-]r-[A-Z-]--[A-Z-]' >/dev/null 2>&1'
    520|1 1 5308422 1 2|Command failed: 'expr "Xprwxrwxrwx" : 'Xprw[a-z]r-[a-z]--[A-Z-]' >/dev/null 2>&1'
    220|1 1 1 07:00:11|FAIL
    200|1 1 07:00:48|TP Start

    200|1 1 07:01:43|TP Start
    520|1 1 5308422 1 1|Assertion #28 (A): When single mode clause has only the op '+'
    520|1 1 5308422 1 1|Command failed: 'expr "Xprwxrwxrwx" : 'Xprw[A-Z-]r-[A-Z-]r-[A-Z-]' >/dev/null 2>&1'
    220|1 1 1 07:01:51|FAIL
    410|1 28 1 07:01:51|IC End
    400|1 29 1 07:01:53|IC Start
    200|1 1 07:01:54|TP Start
    520|1 1 5308422 1 1|Assertion #29 (A): When a single mode clause has op '-' and who and param are specified
    520|1 1 5308422 1 1|Command failed: 'expr "Xprwxrwxr--" : 'Xprw[A-Z-]r-[A-Z-]r-[A-Z-]' >/dev/null 2>&1'
    220|1 1 1 07:02:03|FAIL
    410|1 29 1 07:02:03|IC End
    400|1 30 1 07:02:05|IC Start
    200|1 1 07:02:06|TP Start
    520|1 1 5308422 1 1|Assertion #30 (A): When a single mode clause has op '-' and only param are specified
    520|1 1 5308422 1 1|Command failed: 'expr "Xpr-xr-xr-x" : 'Xpr-[A-Z-]r-[A-Z-]--[A-Z-]' >/dev/null 2>&1'
    220|1 1 1 07:02:14|FAIL
    410|1 30 1 07:02:15|IC End
    400|1 31 1 07:02:18|IC Start
    200|1 1 07:02:19|TP Start
    520|1 1 5308422 1 1|Assertion #31 (A): When single mode clause has only the op '-'
    520|1 1 5308422 1 1|Command failed: 'expr "Xprwxrwxrwx" : 'Xprw[A-Z-]r-[A-Z-]r-[A-Z-]' >/dev/null 2>&1'
    220|1 1 1 07:02:29|FAIL

    200|1 1 07:02:44|TP Start
    520|1 1 5308422 1 1|Assertion #33 (A): When a single mode clause has op '=' and only param are specified
    520|1 1 5308422 1 1|Command failed: 'expr "Xprwxrwxrwx" : 'Xp-w[a-z]--[a-z]--[a-z]' >/dev/null 2>&1'
    220|1 1 1 07:02:54|FAIL

    Review Information

    Review Type TSMA Review
    Start Date null
    Completed null
    Status Complete
    Review Recommendation No Resolution Given
    Review Response
    pasc-1003.2-124 is a pending interpretation request that states

    The interp. request pasc-1003.2-67 (mkdir, Section 4.41)
    identified wording in the standard which was unclear. This
    (almost) identical wording in mkdir also occurs in the
    description for mkfifo.

    Should mkfifo -m mode utilize the current umask in setting permissions?
    Or should the same resolution from interp #67 also apply to mkfifo?

    The 1003.2-1992 rationale for mkfifo says that the -m option was added
    to control the file mode, for consistency with the similar functionality
    provided in the mkdir utility. Hence, I think that the -m option to
    mkfifo should behave similar to the -m option for mkdir.

    We believe the issues with mkfifo are identical to the issues with
    mkdir which resulted in a a pasc-1003.2-67 stating

    The standard is unclear on this issue, and no conformance distinction can
    be made between alternative implementations based on this. This is being
    referred to the sponsor.

    In our opinion, this issue will eventually result in mkfifo's
    interaction with the current umask being undefined when the -m
    option is used.

    A temporary 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