Minutes of the 24th September 2009 Teleconference Austin-466 Page 1 of 1 Submitted by Andrew Josey, The Open Group. September 26 , 2009 Attendees Andrew Josey, The Open Group Don Cragun, PASC OR Geoff Clare, The Open Group Mark Brown, IBM, TOG OR Nick Stoughton, USENIX, ISO/IEC OR Apologies Ulrich Drepper, Red Hat Andrew reported that SC22 has reaffirmed Nick and Keld to continue as organizational representatives (Nick is the primary, with Keld the alternate). We proceeded to review the new bugs in Mantis Mantis #74 , Pointer types http://austingroupbugs.net/view.php?id=74 Don will take an action to update the bug. There is overlap with Austin Group interpretation 1003.1-2001 #003 which is now thought to have issues. In the interpretation response we need to make the following changes. Change from: The XSI margin marking description clearly states that requirements like this are extensions to the requirements of the C Standard. In this case, the 1999 C Standard does indeed require a warning to be issued for the function call shown in the dlsym() examples section on XSH P259, L8566. An equivalent form of this call: *(void **)(&fptr) = dlsym(handle, "my_function"); does not generate compiler warnings and will work correctly on all systems supporting the X/Open System Interfaces Extension. to The XSI margin marking description clearly states that requirements like this are extensions to the requirements of the C Standard. and remove all the notes to the editor This change would need to go for another 30 day for review Action: Andrew to update the interpretation and notify the group #144 Standard lacks a (possibly XSI) interface to associate a session to a TTY; tcsetsid() Resolved as future enhancement http://austingroupbugs.net/view.php?id=144 This will be considered as a possible future enhancement #147 rename and trailing slash Accept as marked http://austingroupbugs.net/view.php?id=147 See note http://austingroupbugs.net/view.php?id=147#c218 #148 pow unclear return value description Accept as marked http://austingroupbugs.net/view.php?id=147 See note http://austingroupbugs.net/view.php?id=147#c225 #149 add fdwalk() system call Future Direction http://austingroupbugs.net/view.php?id=149 See note http://austingroupbugs.net/view.php?id=149#c238 #151 readlink and file times Accepted http://austingroupbugs.net/view.php?id=151 #152 ENV variable and UP/XSI shading Accepted http://austingroupbugs.net/view.php?id=152 #153 waitid() return of 0 is ambiguous Accept http://austingroupbugs.net/view.php?id=153 This should be sent down the interpretations track. "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." #154 waitid() WCONTINUED and WSTOPPED descriptions Accepted http://austingroupbugs.net/view.php?id=154 #155 set -u should require an error when $1 etc. are unset Accept http://austingroupbugs.net/view.php?id=155 This should be sent down the interpretations track. "The standard states "The shell shall write a message to standard error when it tries to expand a variable that is not set and immediately exit." and conforming implementations must conform to this. However, concerns have been raised about this which are being referred to the sponsor." #156 df -k and free inodes Accepted http://austingroupbugs.net/view.php?id=156 This should be sent down the interpretations track. "The standard states the requirement as listed above, and conforming implementations must conform to this. However, concerns have been raised about this which are being referred to the sponsor." While investigating this, we discovered that some XSI-branded implementations do not provide the required inode information, even without the -k option being used. This interpretation request concerns the requirements for the -k case only. The inode information requirement is still in place for the default case. #157 shading of "sa_handler and sa_sigaction may overlap" text Accept http://austingroupbugs.net/view.php?id=157 #140 (Issue 6 bug) Realtime signals delivery order OPEN http://austingroupbugs.net/view.php?id=140 Note 242 was added Would a pointer to sigaction() in the application usage here provide the information you think is needed? The sigaction() pages have a detailed set of information that applies here. Next Steps ---------- The next call will be on October 8 at 16:00 UK time/08:00 Pacific to carry on with the defect reports 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