Austin Group Defect Tracker

Aardvark Mark IV

Main | My View | View Issues | Change Log | Docs
  

Viewing Issue Simple Details [ Jump to Notes ] [ Issue History ] [ Print ]
ID Category Severity Type Date Submitted Last Update
0001416 [1003.1(2016/18)/Issue7+TC2] System Interfaces Editorial Error 2020-11-03 10:45 2021-03-12 11:28
Reporter geoffclare View Status public  
Assigned To
Priority normal Resolution Accepted  
Status Applied  
Name Geoff Clare
Organization The Open Group
User Reference
Section getrlimit()
Page Number 1086
Line Number 36850-36881
Interp Status ---
Final Accepted Text
Summary 0001416: Misuses of "may" on the getrlimit() page
Description The getrlimit() page has some uses of "may" that should be "can" or "shall", as they do not relate to optional behaviour of implementations. (I.e. the word has been used with its informal English-language sense rather than its formal definition in the Terminology section.)

There is some overlap with the bug 0001141 change to the RLIMIT_CORE description, but that is an issue8 tagged bug, and this one should be tagged tc3-2008, so this needs to be retrospectively applied "before" bug 1141.
Desired Action On page 1086 line 36850 section getrlimit(), change:
Soft limits may be changed by a process to any value that is less than or equal to the hard limit. A process may (irreversibly) lower its hard limit to any value that is greater than or equal to the soft limit.
to:
Soft limits can be changed by a process to any value that is less than or equal to the hard limit. A process can (irreversibly) lower its hard limit to any value that is greater than or equal to the soft limit.

On page 1086 line 36861 section getrlimit(), change:
This is the maximum size of a core file, in bytes, that may be created by a process.
to:
This is the maximum size of a core file, in bytes, that can be created by a process.

(Note to the editor: when merging this with the bug 0001141 change, the end result should be just the change from "may" to "can" in the Issue 8 draft text.)

On page 1086 line 36871 section getrlimit(), change:
This is the maximum size of a file, in bytes, that may be created by a process.
to:
This is the maximum size of a file, in bytes, that can be created by a process.

On page 1086 line 36877 section getrlimit(), change:
This is a number one greater than the maximum value that the system may assign to a newly-created descriptor. If this limit is exceeded, functions that allocate a file descriptor shall fail with errno set to [EMFILE]. This limit constrains the number of file descriptors that a process may allocate.
to:
This is a number one greater than the maximum value that the system shall assign to a newly-created descriptor. If this limit is exceeded, functions that allocate a file descriptor shall fail with errno set to [EMFILE]. This limit constrains the number of file descriptors that a process can allocate.
Tags tc3-2008
Attached Files

- Relationships
related to 0001141Applied Add WCOREDUMP(stat) to sys/wait.h 

There are no notes attached to this issue.

- Issue History
Date Modified Username Field Change
2020-11-03 10:45 geoffclare New Issue
2020-11-03 10:45 geoffclare Name => Geoff Clare
2020-11-03 10:45 geoffclare Organization => The Open Group
2020-11-03 10:45 geoffclare Section => getrlimit()
2020-11-03 10:45 geoffclare Page Number => 1086
2020-11-03 10:45 geoffclare Line Number => 36850-36881
2020-11-03 10:45 geoffclare Interp Status => ---
2020-11-03 10:45 geoffclare Desired Action Updated
2020-11-03 10:46 geoffclare Relationship added related to 0001141
2021-02-22 16:34 nick Status New => Resolved
2021-02-22 16:34 nick Resolution Open => Accepted
2021-02-22 16:35 nick Tag Attached: tc3-2008
2021-03-12 11:28 geoffclare Status Resolved => Applied

Mantis 1.1.6[^]
Copyright © 2000 - 2008 Mantis Group
Powered by Mantis Bugtracker