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

The Open Brand -- Problem Reporting and Interpretations System

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

Report 2517 Actions

    Problem Report Number 2517
    Submitter's Classification Specification problem
    State Resolved
    Resolution Test Suite Deficiency (TSD)
    Problem Resolution ID TSD.X.1312
    Raised 2006-06-15 02:58
    Updated 2006-06-17 01:28
    Published 2006-06-17 01:28
    Product Standard Commands and Utilities V4 (UNIX 03)
    Certification Program The Open Brand certification program
    Test Suite VSC version VSC 5.2.7
    Test Identification POSIX.cmd/ed assertions 673, 674, 675
    Specification Shell and Utilities Issue 6
    Location in Spec XCU line 13107, page 340
    Problem Summary Current wording doesn't follow the wording in PASC 1003.2-92 #36
    interpretation request which supposely was used to rewrite this section
    for SUSv4.
    Problem Text I have submitted a defect report(ERN 94) to the Austin working group,
    but currently they have not reviewed the report. I am requesting a TIN
    be issued until the problem can be reviewed.

    The current SUSv3 text for ed has the following wording, which was
    supposed to have come from PASC 1003.2-92 #36 interpretation request.

    If a terminal disconnect is detected:

    - If the buffer is not empty and has changed since the last write,
    the ed utility shall attempt to write a copy of the buffer to a
    file named ed.hup in the current directory. If this write fails,
    ed shall attempt to write a copy of the buffer to a filename
    ed.hup in the directory named by the HOME environment variable.
    If both these attempts fail, ed shall exit without saving the
    buffer.

    - The ed utility shall not write the file to the currently remembered
    pathname or return to command mode, and shall terminate with a
    non-zero exit status.


    If an end-of-file is detected on standard input:

    - If the ed utility is in input mode, ed shall terminate input mode
    and return to command mode. It is unspecified if any partially
    entered lines (that is, input text without a terminating
    <newline>) are discarded from the input text.

    - If the ed utility is in command mode, it shall act as if a q
    command had been entered.

    The text above ( and in POSIX.2b) is quite different from the changes
    in the editors note in 1003.2-92 interp #36, which said:

    "If an end-of-file is detected on standard input when input from the
    user is expected and the standard input is a terminal device, if the
    buffer is not empty and has changed since the last write, the ed
    utility
    shall attempt to write a copy of the buffer to a file. First, the file
    named ed.hup in the current directory shall be used; if that fails, the
    file named ed.hup in the directory named by the HOME environment
    variable shall be used.


    If an end-of-file is detected on standard input when input from the
    user is expected and standard input is not a terminal device, the ed
    utility shall not write the file to the currently remembered pathname
    or return to command mode, and shall terminate with a nonzero exit
    status."


    The current wording requires ed to determine the difference between a
    normal end of file and terminal disconnect when stdin sees an end of
    file and stdin is a terminal. Whereas the original changes suggested
    seem to be much more reasonable, just requiring differentiation if
    stdin
    is a terminal.
    Test Output ***********************************************************************
    /tset/POSIX.cmd/ed/ed_14.ex 673 Failed


    Test Information:
    Assertion #673 (A): Verify that if a terminal disconnect occurs
    while
    ed has a modified buffer, ed writes the buffer to ed.hup
    in
    the current directory
    file ed.hup has not been created in the current directory


    ***********************************************************************

    ***********************************************************************
    /tset/POSIX.cmd/ed/ed_14.ex 674 Failed


    Test Information:
    Assertion #674 (A): Verify that if a terminal disconnect occurs
    while
    ed has a modified buffer, ed writes the buffer to ed.hup
    in
    the current directory
    file ed.hup has not been created in /tsuites/VSC/vsc



    ***********************************************************************

    ***********************************************************************
    /tset/POSIX.cmd/ed/ed_14.ex 675 Failed


    Test Information:
    Assertion #675 (A): Verify that if a terminal disconnect occurs
    while
    ed has a modified buffer and ed cannot write ed.hup in
    the
    current directory and /tsuites/VSC/vsc, then ed does not
    save
    the buffer
    diff of "ed.hup" and "ed_hup_contents":
    *** ed.hup Fri May 26 16:13:24 2006
    --- ed_hup_contents Fri May 26 16:13:30 2006
    ***************
    *** 1 ****
    ! bogus ed.hup file, placed here to force creation of ed.hup in
    $HOME
    --- 1,11 ----
    ! bogus ed.hup file, placed here to prevent creation of ed.hup
    file.
    ! VSC_EOF
    !
    ! # Create a file whose data represents the contents of the data
    file
    after
    ! # manipulation by ed.
    ! cat << VSC_EOF > ed_675_expected
    ! 675: This is an odd line (one).
    ! 675: This is an odd line (three).
    ! 675: This is an odd line (five).
    ! 675: This is an even line (six).
    ! 675: This is an odd line (seven).
    Command failed: 'cmp_show ed.hup ed_hup_contents'


    ***********************************************************************

    Review Information

    Review Type SA Review
    Start Date 2006-06-15 02:58
    Last Updated 2006-06-17 00:42
    Completed 2006-06-17 00:42
    Status Complete
    Review Resolution Temporary Interpretation (TIN)
    Review Conclusion This PR represents an agreed Temporary Interpretation.

    Problem Reporting System Options:

     

    Back   

Contact the Certification Authority