Minutes of the 16 April 2015 Teleconference Austin-703 Page 1 of 1 Submitted by Andrew Josey, The Open Group. 17 April 2015 Attendees: David Clissold, IBM Don Cragun, IEEE OR Mark Ziegast, SHware Systems Andrew Josey, The Open Group Geoff Clare, The Open Group Richard Hansen, BBN Joerg Schilling, FOKUS Fraunhofer Eric Blake, Red Hat Martin Rehak, Oracle Roger Faulkner , Oracle, The Open Group OR Nick Stoughton, USENIX, ISO/IEC JTC 1/SC 22 OR Apologies: Mark Brown, Canonical * General news Andrew plans to release the first committee draft for a four week review shortly. He explained that for expedience it will be on an interim template before we move to the Microsoft Word based IEEE template later - the word template requires additional checking when flowing in html, whereas an OpenOffice version handles the layout and display correctly. Andrew has setup the 2008-TC2 project in mantis (similarly configured as we did for 2008-TC1) The status of bug 663 was raised (David's action) - David is trying to make contact with the right person in the z/OS team. * Outstanding actions ( Please note that I have flushed this section to shorten the minutes - to locate the last set of outstanding actions, look to the minutes from 26 Feb 2015) Bug 0000887: printf and other functions appear many times in search results OPEN http://austingroupbugs.net/view.php?id=887 Andrew is investigating. Bug 0000900: add qsort_r OPEN http://austingroupbugs.net/view.php?id=900 The consensus was that its a good idea to add the suggested interface. The usual requirements regarding a sponsor for a new interface apply. Action: Open Group OR , to ask the Base WG if they wish to sponsor the additional qsort interface proposed here. Bug 0000901: reserve _POSIX* shell option namespace for future use OPEN http://austingroupbugs.net/view.php?id=901 The forward plan for this bug remains as before: Richard: file a new bug report with a concrete feature that would use the _POSIX* namespace (as motivation for reserving set -o _POSIX*) All: debate the proposed feature. If it's something we want, then revisit bug #901. If not, close bug #901. * Current Business Bug #863: Explicitly disallow longjmp from pthread_once init_routine Accepted as Marked http://austingroupbugs.net/view.php?id=863 This item had been reopened after an email discussion. This item is tagged for TC2-2008 On Page: 1684 Line: 54487 Section: pthread_once() In the DESCRIPTION section, add new paragraph: If the call to init_routine is terminated by a call to longjmp(), _longjmp(), or siglongjmp(), the behavior is undefined. On Page: 1684 Line: 54499 Section: pthread_once() In the APPLICATION USAGE section, change from: None. to: If init_routine recursively calls pthread_once() with the same once_control, the recursive call will not call the specified init_routine, and thus the specified init_routine will not complete, and thus the recursive call to pthread_once() will not return. Use of longjmp(), _longjmp(), or siglongjmp() within an init_routine to jump to a point outside of init_routine prevents init_routine from returning. Cross-volume change to XBD... On Page: 110 Line: 3004 Section: 4.11 Memory Synchronization Change from: The pthread_once() function shall synchronize memory for the first call in each thread for a given pthread_once_t object. to: The pthread_once() function shall synchronize memory for the first call in each thread for a given pthread_once_t object. If the init_routine called by pthread_once() is a cancellation point and is canceled, a call to pthread_once() for the same pthread_once_t object made from a cancellation cleanup handler shall also synchronize memory. Bug #917: specified 'logger' does not match actual usage Accepted as Marked http://austingroupbugs.net/view.php?id=917 This item is tagged for Issue 8 On page 2878 line 94786 (logger synopsis), change: logger string... to: logger [-i] [-f file] [-p priority] [-t tag] [string...] On page 2878 lines 94788-94790 (logger DESCRIPTION), change: The logger utility saves a message, in an unspecified manner and format, containing the string operands provided by the user. The messages are expected to be evaluated later by personnel performing system administration tasks. to: The logger utility shall send messages to an implementation-defined logging facility, which may log them in an implementation-defined system log, write them to the system console, forward them to a list of users, or forward them to the logging facility on another host over the network. Each logged message shall include a message header and a message body. The message header contains at least a timestamp and a tag string. If one or more string operands are specified, they shall be logged; otherwise, the message bodies to be logged shall be read from standard input if no -f option is specified, or from the specified file if the -f option is present. On page 2878 line 94794 (logger options), change: None. to: The logger utility shall conform to XBD Section 12.2 (on page 215). The following options shall be supported: -f file Read the log message bodies from file instead of standard input. -i Log the process ID of the logger process with each message. -p priority Log the message with priority set to priority. The priority is specified as a facility.level pair. The following values for facility shall be supported: user Messages generated by arbitrary processes. local0 Reserved for local use. local1 Reserved for local use. local2 Reserved for local use. local3 Reserved for local use. local4 Reserved for local use. local5 Reserved for local use. local6 Reserved for local use. local7 Reserved for local use. The following values for level shall be supported: emerg A panic condition. alert A condition that should be corrected immediately, such as a corrupted system database. crit Critical conditions, such as hard device errors. err Errors. warning Warning messages. notice Conditions that are not error conditions, but that may require special handling. info Informational messages. debug Messages that contain information normally of use only when debugging a program. If the -p option is not specified, the priority shall be user.notice. -t tag Use the string tag as the tag string in the message header. The default tag is unspecified. On page 2878 line 94800 (logger STDIN), change: Not used. to: The standard input shall be used if no string operands are specified and either the -f option is not specified or the -f option is specified with a file option-argument of '-' and the implementation treats the '-' as meaning standard input. Otherwise, the standard input shall not be used. See the INPUT FILES section. Each non-empty line shall be logged as a separate message. It is unspecified whether an empty line is also logged as a separate message. On page 2878 line 94802 (logger input files), change: None. to: The input files shall be text files. Bug #930: Misuse of italic "destination" in ln description OPEN http://austingroupbugs.net/view.php?id=930 (left open from a previous week) Next Steps ---------- The next call is on April 23, 2015 (a Thursday) (Apologies from Andrew for the next call) Calls are anchored on US time. (8am Pacific) This call will be for the regular 90 minutes. http://austingroupbugs.net An IRC channel will be available for the meeting irc://irc.freenode.net/austingroupbugs An etherpad is usually up for the meeting, with a URL using the date format as below: http://posix@posix.rhansen.org:9001/p/201x-mm-dd password=2115756#