Minutes of the 1st September 2011 Teleconference Austin-536 Page 1 of 1 Submitted by Andrew Josey, The Open Group. September 2 , 2011 Attendees Andrew Josey, The Open Group Don Cragun, PASC OR Mark Brown, IBM, TOG OR Eric Blake, Red Hat Jim Pugsley, Oracle Geoff Clare, The Open Group Matthew Dempsky, Apologies Nick Stoughton, USENIX, ISO/IEC OR Action: Andrew to ship final TC1 draft 3 to IEEE for mandatory editorial coordination. OPEN * Old Business Bug 281 sort -M http://austingroupbugs.net/view.php?id=281 Some discussion had occurred by email and one possible action will be to look at markings on the online specifications, to make it clear that a standalone web page should not be read in isolation, and that other parts of the standard should be read in conjunction to understand all the requirements and nuances of a page of the standard. This could be done by adding a line or link to the header section. It was also suggested that we consider updating the headers of online pages from earlier versions of the standard, so they carry a notice of the existence of a later version of the standard. Don agreed to take an action to propose some wording for a header notice. * New Business * Issue 7 bugs Bug 0000485: Unclear explanation about when last file status change timestamp shall be updated Accepted as Marked http://austingroupbugs.net/view.php?id=485 This item is tagged for TC2-2008. An interpretation is required. Interpretation response: 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. Rationale: The standard requires that timestamps be marked for update even when values being written are identical to what is already present. However, it is unclear whether utimensat is required to write anything when both arguments use UTIME_OMIT, and the wording for chown when both arguments are -1 was difficult to follow. The intent is that implementations may, but not must, optimize these two cases. Notes to the Editor (not part of this interpretation): Make the following changes: Change the wording in the Description section for utimensat() and futimens() [line 32407] from: "Upon completion, futimens() and utimensat() shall mark the last file status change timestamp for update." to: "Upon successful completion, futimens() and utimensat() shall mark the last file status change timestamp for update, with the exception that if both tv_nsec fields are set to UTIME_OMIT, the file status change timestamp need not be marked for update." Change the wording in the Description section for chown() and fchownat() [line 22337] from: "If owner or group is specified as (uid_t)−1 or (gid_t)−1, respectively, the corresponding ID of the file shall not be changed. If both owner and group are −1, the times need not be updated. Upon successful completion, chown( ) shall mark for update the last file status change timestamp of the file." to: "If owner or group is specified as (uid_t)−1 or (gid_t)−1, respectively, the corresponding ID of the file shall not be changed. Upon successful completion, chown( ) shall mark for update the last file status change timestamp of the file, except that if owner is (uid_t)-1 and group is (gid_t)−1, the file status change timestamp need not be marked for update." Bug 0000484: Ambiguity of "first lock" in F_GETLK Accepted http://austingroupbugs.net/view.php?id=484 This item is tagged for TC2-2008 Bug 0000465: is the list of special built-ins exhaustive (is "local" special)? OPEN http://austingroupbugs.net/view.php?id=465 We need further input on this item. Andrew will ping Dave Korn to see if he can assist. Bug 486 0000486: Contradictory comparison of link() and linkat() behaviors Duplicate http://austingroupbugs.net/view.php?id=486 This has handled by making this issue a duplicate of Bug 326, and by changing the resolution of 0000326 as suggested in Note: 0000940. It should be noted that Bug 326 is being fixed in TC1. A separate bug will be filed against TC1-2008 to ensure we take the change into the TC1 draft. Bug 0000326: linkat() equivalence to link() exception insufficient Accepted as Marked http://austingroupbugs.net/view.php?id=326 This bug has been updated as a result of bug 486. A new note is added: Make the change in the desired action and also at line 40136 change: the behavior shall be identical to a call to link() to: the behavior shall be identical to a call to link(), except that symbolic links shall be handled as specified by the value of flag Bug 0000490: Missed change. OPEN http://austingroupbugs.net/view.php?id=490 This bug has been filed against TC1-2008 Draft 3 to record the above change. Bug 487 0000487: Contradictory comparison of access() and faccessat() behaviors OPEN http://austingroupbugs.net/view.php?id=487 Geoff took an action to propose some wording for this item. This is included in bug 951 (text below) Change If faccessat() is passed the special value AT_FDCWD in the fd parameter, the current working directory is used and the behavior shall be identical to a call to access(). to: If faccessat() is passed the special value AT_FDCWD in the fd parameter, the current working directory shall be used and, if flag is zero, the behavior shall be identical to a call to access(). At line 19457 change: The faccessat() function shall be equivalent to the access() function, except in the case where path specifies a relative path. to: The faccessat() function shall be equivalent to the access() function, except that the behavior shall be modified by the value of flag as described below, and except in the case where path specifies a relative path. Next Steps ---------- The next call is on September 8th at 08:00 Pacific and will continue processing defect reports. This call will be for the regular 90 minutes. http://austingroupbugs.net See the calendar for the list of dialup numbers. An IRC channel will be available for the meeting irc://irc.freestandards.org #austin ICAL: http://www.google.com/calendar/ical/nvctqtstkuni3fab9k3jqtrt4g@group.calendar.google.com/public/basic XML: http://www.google.com/calendar/feeds/nvctqtstkuni3fab9k3jqtrt4g@group.calendar.google.com/public/basic