[1003.1(2016)/Issue7+TC2 0001311]: j command incorrectly referred to in ed's rationale section

2019-12-20 Thread Austin Group Bug Tracker


A NOTE has been added to this issue. 
== 
http://austingroupbugs.net/view.php?id=1311 
== 
Reported By:andras_farkas
Assigned To:
== 
Project:1003.1(2016)/Issue7+TC2
Issue ID:   1311
Category:   Shell and Utilities
Type:   Error
Severity:   Editorial
Priority:   normal
Status: New
Name:   Andras Farkas 
Organization:
User Reference:  
Section:ed 
Page Number:ed 
Line Number:1200 
Interp Status:  --- 
Final Accepted Text: 
== 
Date Submitted: 2019-12-20 10:09 UTC
Last Modified:  2019-12-20 10:11 UTC
== 
Summary:j command incorrectly referred to in ed's rationale
section
== 

-- 
 (0004694) andras_farkas (reporter) - 2019-12-20 10:11
 http://austingroupbugs.net/view.php?id=1311#c4694 
-- 
The defect tracker swallowed up the HTML (which I didn't intend to have
rendered) and I can't figure out how to edit the issue. 

Issue History 
Date ModifiedUsername   FieldChange   
== 
2019-12-20 10:09 andras_farkas  New Issue
2019-12-20 10:09 andras_farkas  Name  => Andras Farkas   
2019-12-20 10:09 andras_farkas  Section   => ed  
2019-12-20 10:09 andras_farkas  Page Number   => ed  
2019-12-20 10:09 andras_farkas  Line Number   => 1200
2019-12-20 10:11 andras_farkas  Note Added: 0004694  
==




[1003.1(2016)/Issue7+TC2 0001311]: j command incorrectly referred to in ed's rationale section

2019-12-20 Thread Austin Group Bug Tracker


The following issue has been SUBMITTED. 
== 
http://austingroupbugs.net/view.php?id=1311 
== 
Reported By:andras_farkas
Assigned To:
== 
Project:1003.1(2016)/Issue7+TC2
Issue ID:   1311
Category:   Shell and Utilities
Type:   Error
Severity:   Editorial
Priority:   normal
Status: New
Name:   Andras Farkas 
Organization:
User Reference:  
Section:ed 
Page Number:ed 
Line Number:1200 
Interp Status:  --- 
Final Accepted Text: 
== 
Date Submitted: 2019-12-20 10:09 UTC
Last Modified:  2019-12-20 10:09 UTC
== 
Summary:j command incorrectly referred to in ed's rationale
section
Description: 
In the rationale section on ed's page (
https://pubs.opengroup.org/onlinepubs/9699919799/utilities/ed.html ) we
see:
On BSD, the join command with only a single address changes the current
line to that address.
In the HTML:

On BSD, the join command
with only a single address changes the current line to that
address.

This link to the join utility is incorrect.  ed's j command is intended.

(unrelatedly, it's odd that  is being used within  when LI elements
already accept text content in HTML)
Desired Action: 
The text should be changed as follows:
On BSD, the j command with only a single address changes the current line
to that address.
The HTML should be changed as follows:

On BSD, the j command with only a single address changes the
current line to that
address.

== 

Issue History 
Date ModifiedUsername   FieldChange   
== 
2019-12-20 10:09 andras_farkas  New Issue
2019-12-20 10:09 andras_farkas  Name  => Andras Farkas   
2019-12-20 10:09 andras_farkas  Section   => ed  
2019-12-20 10:09 andras_farkas  Page Number   => ed  
2019-12-20 10:09 andras_farkas  Line Number   => 1200
==




[1003.1(2016)/Issue7+TC2 0001311]: j command incorrectly referred to in ed's rationale section

2019-12-20 Thread Austin Group Bug Tracker


The following issue has been UPDATED. 
== 
http://austingroupbugs.net/view.php?id=1311 
== 
Reported By:andras_farkas
Assigned To:
== 
Project:1003.1(2016)/Issue7+TC2
Issue ID:   1311
Category:   Shell and Utilities
Type:   Error
Severity:   Editorial
Priority:   normal
Status: New
Name:   Andras Farkas 
Organization:
User Reference:  
Section:ed 
Page Number:2689 
Line Number:87741 
Interp Status:  --- 
Final Accepted Text: 
== 
Date Submitted: 2019-12-20 10:09 UTC
Last Modified:  2019-12-20 10:27 UTC
== 
Summary:j command incorrectly referred to in ed's rationale
section
== 

Issue History 
Date ModifiedUsername   FieldChange   
== 
2019-12-20 10:09 andras_farkas  New Issue
2019-12-20 10:09 andras_farkas  Name  => Andras Farkas   
2019-12-20 10:09 andras_farkas  Section   => ed  
2019-12-20 10:09 andras_farkas  Page Number   => ed  
2019-12-20 10:09 andras_farkas  Line Number   => 1200
2019-12-20 10:11 andras_farkas  Note Added: 0004694  
2019-12-20 10:27 geoffclare Page Number  ed => 2689  
2019-12-20 10:27 geoffclare Line Number  1200 => 87741   
2019-12-20 10:27 geoffclare Interp Status => --- 
2019-12-20 10:27 geoffclare Description Updated  
2019-12-20 10:27 geoffclare Desired Action Updated   
==




[1003.1(2016)/Issue7+TC2 0001311]: j command incorrectly referred to in ed's rationale section

2019-12-20 Thread Austin Group Bug Tracker


A NOTE has been added to this issue. 
== 
http://austingroupbugs.net/view.php?id=1311 
== 
Reported By:andras_farkas
Assigned To:
== 
Project:1003.1(2016)/Issue7+TC2
Issue ID:   1311
Category:   Shell and Utilities
Type:   Error
Severity:   Editorial
Priority:   normal
Status: New
Name:   Andras Farkas 
Organization:
User Reference:  
Section:ed 
Page Number:2689 
Line Number:87741 
Interp Status:  --- 
Final Accepted Text: 
== 
Date Submitted: 2019-12-20 10:09 UTC
Last Modified:  2019-12-20 10:27 UTC
== 
Summary:j command incorrectly referred to in ed's rationale
section
== 

-- 
 (0004695) shware_systems (reporter) - 2019-12-20 10:27
 http://austingroupbugs.net/view.php?id=1311#c4695 
-- 
Mantis understands a subset of HTML tags, so when you want them to show as
plain text you need to add a SPC or '_' after the '<' opening each tag.
Except for the last part what's there now is understandable anyways. 

Issue History 
Date ModifiedUsername   FieldChange   
== 
2019-12-20 10:09 andras_farkas  New Issue
2019-12-20 10:09 andras_farkas  Name  => Andras Farkas   
2019-12-20 10:09 andras_farkas  Section   => ed  
2019-12-20 10:09 andras_farkas  Page Number   => ed  
2019-12-20 10:09 andras_farkas  Line Number   => 1200
2019-12-20 10:11 andras_farkas  Note Added: 0004694  
2019-12-20 10:27 geoffclare Page Number  ed => 2689  
2019-12-20 10:27 geoffclare Line Number  1200 => 87741   
2019-12-20 10:27 geoffclare Interp Status => --- 
2019-12-20 10:27 geoffclare Description Updated  
2019-12-20 10:27 geoffclare Desired Action Updated   
2019-12-20 10:27 shware_systems Note Added: 0004695  
==




[1003.1(2016)/Issue7+TC2 0001311]: j command incorrectly referred to in ed's rationale section

2019-12-20 Thread Austin Group Bug Tracker


A NOTE has been added to this issue. 
== 
http://austingroupbugs.net/view.php?id=1311 
== 
Reported By:andras_farkas
Assigned To:
== 
Project:1003.1(2016)/Issue7+TC2
Issue ID:   1311
Category:   Shell and Utilities
Type:   Error
Severity:   Editorial
Priority:   normal
Status: New
Name:   Andras Farkas 
Organization:
User Reference:  
Section:ed 
Page Number:2689 
Line Number:87741 
Interp Status:  --- 
Final Accepted Text: 
== 
Date Submitted: 2019-12-20 10:09 UTC
Last Modified:  2019-12-20 10:33 UTC
== 
Summary:j command incorrectly referred to in ed's rationale
section
== 

-- 
 (0004697) andras_farkas (reporter) - 2019-12-20 10:33
 http://austingroupbugs.net/view.php?id=1311#c4697 
-- 
I see.  Thanks! :D 

Issue History 
Date ModifiedUsername   FieldChange   
== 
2019-12-20 10:09 andras_farkas  New Issue
2019-12-20 10:09 andras_farkas  Name  => Andras Farkas   
2019-12-20 10:09 andras_farkas  Section   => ed  
2019-12-20 10:09 andras_farkas  Page Number   => ed  
2019-12-20 10:09 andras_farkas  Line Number   => 1200
2019-12-20 10:11 andras_farkas  Note Added: 0004694  
2019-12-20 10:27 geoffclare Page Number  ed => 2689  
2019-12-20 10:27 geoffclare Line Number  1200 => 87741   
2019-12-20 10:27 geoffclare Interp Status => --- 
2019-12-20 10:27 geoffclare Description Updated  
2019-12-20 10:27 geoffclare Desired Action Updated   
2019-12-20 10:27 shware_systems Note Added: 0004695  
2019-12-20 10:29 geoffclare Note Added: 0004696  
2019-12-20 10:29 geoffclare Description Updated  
2019-12-20 10:30 geoffclare Note Edited: 0004696 
2019-12-20 10:33 andras_farkas  Note Added: 0004697  
==




[1003.1(2016)/Issue7+TC2 0001311]: j command incorrectly referred to in ed's rationale section

2019-12-20 Thread Austin Group Bug Tracker


The following issue has been UPDATED. 
== 
http://austingroupbugs.net/view.php?id=1311 
== 
Reported By:andras_farkas
Assigned To:
== 
Project:1003.1(2016)/Issue7+TC2
Issue ID:   1311
Category:   Shell and Utilities
Type:   Error
Severity:   Editorial
Priority:   normal
Status: New
Name:   Andras Farkas 
Organization:
User Reference:  
Section:ed 
Page Number:2689 
Line Number:87741 
Interp Status:  --- 
Final Accepted Text: 
== 
Date Submitted: 2019-12-20 10:09 UTC
Last Modified:  2019-12-20 10:29 UTC
== 
Summary:j command incorrectly referred to in ed's rationale
section
== 

-- 
 (0004696) geoffclare (manager) - 2019-12-20 10:29
 http://austingroupbugs.net/view.php?id=1311#c4696 
-- 
I have fixed the HTMl problem in description and desired action by changing
'<' to '['. 

Issue History 
Date ModifiedUsername   FieldChange   
== 
2019-12-20 10:09 andras_farkas  New Issue
2019-12-20 10:09 andras_farkas  Name  => Andras Farkas   
2019-12-20 10:09 andras_farkas  Section   => ed  
2019-12-20 10:09 andras_farkas  Page Number   => ed  
2019-12-20 10:09 andras_farkas  Line Number   => 1200
2019-12-20 10:11 andras_farkas  Note Added: 0004694  
2019-12-20 10:27 geoffclare Page Number  ed => 2689  
2019-12-20 10:27 geoffclare Line Number  1200 => 87741   
2019-12-20 10:27 geoffclare Interp Status => --- 
2019-12-20 10:27 geoffclare Description Updated  
2019-12-20 10:27 geoffclare Desired Action Updated   
2019-12-20 10:27 shware_systems Note Added: 0004695  
2019-12-20 10:29 geoffclare Note Added: 0004696  
2019-12-20 10:29 geoffclare Description Updated  
==




[1003.1(2016)/Issue7+TC2 0001312]: ctags -v example in ctags's rationale section missing a newline

2019-12-20 Thread Austin Group Bug Tracker


The following issue has been SUBMITTED. 
== 
http://austingroupbugs.net/view.php?id=1312 
== 
Reported By:andras_farkas
Assigned To:
== 
Project:1003.1(2016)/Issue7+TC2
Issue ID:   1312
Category:   Shell and Utilities
Type:   Error
Severity:   Editorial
Priority:   normal
Status: New
Name:   Andras Farkas 
Organization:
User Reference:  
Section:ctags 
Page Number: 
Line Number: 
Interp Status:  --- 
Final Accepted Text: 
== 
Date Submitted: 2019-12-20 10:49 UTC
Last Modified:  2019-12-20 10:49 UTC
== 
Summary:ctags -v example in ctags's rationale section
missing a newline
Description: 
In the rationale section of ctags (
https://pubs.opengroup.org/onlinepubs/9699919799/utilities/ctags.html )
there's an example about ctags -v and vgrind:

ctags -v files | sort -f > index vgrind -x index

It's missing a newline which is required for example to run. (alternatively
a ; or && could be used)
Desired Action: 
Simply change it to the following, by adding a newline or BR HTML tag:

ctags -v files | sort -f > index
vgrind -x index
== 

Issue History 
Date ModifiedUsername   FieldChange   
== 
2019-12-20 10:49 andras_farkas  New Issue
2019-12-20 10:49 andras_farkas  Name  => Andras Farkas   
2019-12-20 10:49 andras_farkas  Section   => ctags   
==




[1003.1(2008)/Issue 7 0000169]: date utility needs ``%s''

2019-12-20 Thread Austin Group Bug Tracker


The following issue has a resolution that has been APPLIED. 
== 
http://austingroupbugs.net/view.php?id=169 
== 
Reported By:wpollock
Assigned To:ajosey
== 
Project:1003.1(2008)/Issue 7
Issue ID:   169
Category:   Shell and Utilities
Type:   Enhancement Request
Severity:   Editorial
Priority:   normal
Status: Applied
Name:   Wayne Pollock 
Organization:
User Reference:  
Section:date 
Page Number:NA 
Line Number:NA 
Interp Status:  --- 
Final Accepted Text:http://austingroupbugs.net/view.php?id=169#c283 
Resolution: Accepted As Marked
Fixed in Version:   
== 
Date Submitted: 2009-10-15 15:44 UTC
Last Modified:  2019-12-20 11:55 UTC
== 
Summary:date utility needs ``%s''
==
Relationships   ID  Summary
--
related to  047 Missing specifiers for date utility
related to  466 date +%C problem
related to  954 Add %s to strftime
== 

Issue History 
Date ModifiedUsername   FieldChange   
== 
2009-10-15 15:44 wpollock   New Issue
2009-10-15 15:44 wpollock   Status   New => Under Review 
2009-10-15 15:44 wpollock   Assigned To   => ajosey  
2009-10-15 15:44 wpollock   Name  => Wayne Pollock   
2009-10-15 15:44 wpollock   Section   => date
2009-10-15 15:44 wpollock   Page Number   => NA  
2009-10-15 15:44 wpollock   Line Number   => NA  
2009-10-15 15:45 wpollock   Issue Monitored: wpollock
2009-10-16 09:07 geoffclare Note Added: 262  
2009-10-16 09:07 geoffclare Note Edited: 262 
2009-10-16 09:12 geoffclare Note Edited: 262 
2009-11-05 16:51 msbrownInterp Status => --- 
2009-11-05 16:51 msbrownResolution   Open => Future
Enhancement
2009-11-05 16:52 Don Cragun Note Added: 283  
2009-11-05 16:54 Don Cragun Final Accepted Text   =>
http://austingroupbugs.net/view.php?id=169#c283 
2009-11-05 16:54 Don Cragun Status   Under Review =>
Resolved
2010-09-09 15:47 geoffclare Tag Attached: issue8 
2011-06-24 21:00 eblake Relationship added   related to 047  
2011-06-24 21:13 eblake Relationship added   related to 466  
2011-06-30 16:23 Don Cragun Note Edited: 283 
2011-06-30 16:49 eblake Tag Attached: c99
2011-07-08 15:59 Don Cragun Resolution   Future Enhancement =>
Accepted As Marked
2015-06-04 08:31 geoffclare Relationship added   related to 954  
2016-02-25 16:45 Don Cragun Note Edited: 283 
2016-02-25 16:48 Don Cragun Note Edited: 283 
2016-02-25 16:49 Don Cragun Note Edited: 283 
2019-12-20 11:55 geoffclare Status   Resolved => Applied 
==




[1003.1(2008)/Issue 7 0000188]: thread-safe getenv()

2019-12-20 Thread Austin Group Bug Tracker


The following issue has a resolution that has been APPLIED. 
== 
http://austingroupbugs.net/view.php?id=188 
== 
Reported By:geoffclare
Assigned To:ajosey
== 
Project:1003.1(2008)/Issue 7
Issue ID:   188
Category:   System Interfaces
Type:   Enhancement Request
Severity:   Objection
Priority:   normal
Status: Applied
Name:   Geoff Clare 
Organization:   The Open Group 
User Reference:  
Section:getenv 
Page Number:1008 
Line Number:33858 
Interp Status:  Approved 
Final Accepted Text:http://austingroupbugs.net/view.php?id=188#c325 
Resolution: Accepted As Marked
Fixed in Version:   
== 
Date Submitted: 2009-11-26 10:50 UTC
Last Modified:  2019-12-20 12:00 UTC
== 
Summary:thread-safe getenv()
== 

Issue History 
Date ModifiedUsername   FieldChange   
== 
2009-11-26 10:50 geoffclare New Issue
2009-11-26 10:50 geoffclare Status   New => Under Review 
2009-11-26 10:50 geoffclare Assigned To   => ajosey  
2009-11-26 10:50 geoffclare Name  => Geoff Clare 
2009-11-26 10:50 geoffclare Organization  => The Open Group  
2009-11-26 10:50 geoffclare Section   => getenv  
2009-11-26 10:50 geoffclare Page Number   => 1008
2009-11-26 10:50 geoffclare Line Number   => 33858   
2009-11-26 10:50 geoffclare Interp Status => --- 
2009-11-26 16:25 drepperNote Added: 309  
2009-12-01 10:11 geoffclare Note Added: 311  
2009-12-02 19:04 msbrownNote Added: 313  
2009-12-10 16:35 msbrownInterp Status--- => Pending  
2009-12-10 16:35 msbrownNote Added: 325  
2009-12-10 16:35 msbrownType Error => Enhancement
Request
2009-12-10 16:35 msbrownStatus   Under Review =>
Interpretation Required
2009-12-10 16:35 msbrownResolution   Open => Accepted As
Marked
2009-12-10 16:35 msbrownDescription Updated  
2009-12-10 16:35 msbrownFinal Accepted Text   =>
http://austingroupbugs.net/view.php?id=188#c325 
2010-02-12 06:38 ajosey Interp StatusPending => Proposed 
2010-03-25 15:15 geoffclare Note Edited: 325 
2010-03-25 15:16 geoffclare Interp StatusProposed => Approved
2010-09-24 14:42 Don Cragun Tag Attached: issue8 
2019-12-20 12:00 geoffclare Status   Interpretation Required
=> Applied
==




[1003.1(2008)/Issue 7 0000190]: Require environment variables and exit status information to man pages

2019-12-20 Thread Austin Group Bug Tracker


The following issue has a resolution that has been APPLIED. 
== 
http://austingroupbugs.net/view.php?id=190 
== 
Reported By:adelfino
Assigned To:ajosey
== 
Project:1003.1(2008)/Issue 7
Issue ID:   190
Category:   Shell and Utilities
Type:   Enhancement Request
Severity:   Editorial
Priority:   normal
Status: Applied
Name:   Andrés Delfino 
Organization:
User Reference:  
Section:man utility 
Page Number:2930 
Line Number:96402 to 96404 (including both) 
Interp Status:  --- 
Final Accepted Text:See http://austingroupbugs.net/view.php?id=190#c320 
Resolution: Accepted As Marked
Fixed in Version:   
== 
Date Submitted: 2009-12-03 02:27 UTC
Last Modified:  2019-12-20 12:04 UTC
== 
Summary:Require environment variables and exit status
information to man pages
== 

Issue History 
Date ModifiedUsername   FieldChange   
== 
2009-12-03 02:27 adelfino   New Issue
2009-12-03 02:27 adelfino   Status   New => Under Review 
2009-12-03 02:27 adelfino   Assigned To   => ajosey  
2009-12-03 02:27 adelfino   Name  => Andrés Delfino 
2009-12-03 02:27 adelfino   Section   => man utility 
2009-12-03 02:27 adelfino   Page Number   => 2930
2009-12-03 02:27 adelfino   Line Number   => 96402 to 96404
(including both)
2009-12-03 17:12 nick   Note Added: 319  
2009-12-03 17:25 Don Cragun Interp Status => --- 
2009-12-03 17:25 Don Cragun Note Added: 320  
2009-12-03 17:25 Don Cragun Status   Under Review =>
Resolved
2009-12-03 17:25 Don Cragun Resolution   Open => Accepted As
Marked
2009-12-03 17:27 Don Cragun Final Accepted Text   => See
http://austingroupbugs.net/view.php?id=190#c320 
2010-09-09 15:38 Don Cragun Tag Attached: tc1-2008   
2010-09-09 15:39 Don Cragun Tag Detached: tc1-2008   
2010-09-09 15:40 Don Cragun Tag Attached: issue8 
2010-09-09 15:41 Don Cragun Resolution   Accepted As Marked =>
Future Enhancement
2011-07-08 16:00 Don Cragun Resolution   Future Enhancement =>
Accepted As Marked
2011-07-08 16:00 Don Cragun Summary  Requiere environment
variables and exit status information to man pages => Require environment
variables and exit status information to man pages
2011-07-09 01:37 wpollock   Note Added: 889  
2011-07-10 04:20 user143Note Added: 890  
2011-07-10 04:24 user143Note Edited: 890 
2011-07-10 04:24 user143Note Edited: 890 
2011-07-10 04:25 user143Note Edited: 890 
2011-07-10 04:26 user143Note Edited: 890 
2011-07-10 04:27 user143Note Edited: 890 
2011-07-10 04:27 user143Note Edited: 890 
2011-07-10 04:27 user143Note Edited: 890 
2011-07-10 04:28 user143Note Edited: 890 
2019-12-20 12:04 geoffclare Status   Resolved => Applied 
==




[1003.1(2008)/Issue 7 0000191]: getopt and leading + in optstring

2019-12-20 Thread Austin Group Bug Tracker


The following issue has a resolution that has been APPLIED. 
== 
http://austingroupbugs.net/view.php?id=191 
== 
Reported By:eblake
Assigned To:ajosey
== 
Project:1003.1(2008)/Issue 7
Issue ID:   191
Category:   System Interfaces
Type:   Enhancement Request
Severity:   Comment
Priority:   normal
Status: Applied
Name:   Eric Blake 
Organization:   NA 
User Reference: ebb.getopt2 
Section:getopt 
Page Number:1040 
Line Number:34822 
Interp Status:  --- 
Final Accepted Text:See http://austingroupbugs.net/view.php?id=191#c329 
Resolution: Accepted As Marked
Fixed in Version:   
== 
Date Submitted: 2009-12-03 03:38 UTC
Last Modified:  2019-12-20 12:09 UTC
== 
Summary:getopt and leading + in optstring
== 

Issue History 
Date ModifiedUsername   FieldChange   
== 
2009-12-03 03:38 eblake New Issue
2009-12-03 03:38 eblake Status   New => Under Review 
2009-12-03 03:38 eblake Assigned To   => ajosey  
2009-12-03 03:38 eblake Name  => Eric Blake  
2009-12-03 03:38 eblake Organization  => NA  
2009-12-03 03:38 eblake User Reference=> ebb.getopt2 
2009-12-03 03:38 eblake Section   => getopt  
2009-12-03 03:38 eblake Page Number   => 1040
2009-12-03 03:38 eblake Line Number   => 34822   
2009-12-03 14:03 eblake Note Added: 315  
2009-12-03 16:02 eblake Note Added: 316  
2009-12-10 16:58 nick   Note Added: 326  
2009-12-11 13:31 eblake Note Added: 329  
2010-01-07 16:23 Don Cragun Note Edited: 329 
2010-01-07 16:24 Don Cragun Interp Status => --- 
2010-01-07 16:24 Don Cragun Final Accepted Text   => See
http://austingroupbugs.net/view.php?id=191#c329 
2010-01-07 16:24 Don Cragun Status   Under Review =>
Resolved
2010-01-07 16:24 Don Cragun Resolution   Open => Accepted As
Marked
2010-09-09 15:41 Don Cragun Tag Attached: issue8 
2010-09-09 15:42 Don Cragun Resolution   Accepted As Marked =>
Future Enhancement
2011-07-08 16:01 Don Cragun Resolution   Future Enhancement =>
Accepted As Marked
2019-12-20 12:09 geoffclare Status   Resolved => Applied 
==




Austin Group teleconference +1 888 974 9888 PIN 618 156 403

2019-12-20 Thread Single UNIX Specification
BEGIN:VCALENDAR
VERSION:2.0
PRODID:-//opengroup.org//NONSGML kigkonsult.se iCalcreator 2.22.1//
CALSCALE:GREGORIAN
METHOD:REQUEST
BEGIN:VTIMEZONE
TZID:America/New_York
X-LIC-LOCATION:America/New_York
BEGIN:DAYLIGHT
TZOFFSETFROM:-0500
TZOFFSETTO:-0400
TZNAME:EDT
DTSTART:20120311T02
RRULE:FREQ=YEARLY;BYMONTH=3;BYDAY=2SU
END:DAYLIGHT
BEGIN:STANDARD
TZOFFSETFROM:-0400
TZOFFSETTO:-0500
TZNAME:EST
DTSTART:20121104T02
RRULE:FREQ=YEARLY;BYMONTH=11;BYDAY=1SU
END:STANDARD
END:VTIMEZONE
BEGIN:VEVENT
UID:5dfd0ab038...@opengroup.org
DTSTAMP:20191220T175352Z
ATTENDEE;ROLE=CHAIR:MAILTO:a.jo...@opengroup.org
CREATED:20191220T00Z
DESCRIPTION:Web/Project: Single UNIX Specification\nTitle: Austin Group tel
 econference +1 888 974 9888 PIN 618 156 403\nDate/Time: 09-Jan-2020 at 11:
 00 America/New_York\nDuration: 1.50 hours\nURL: https://collaboration.open
 group.org/platform/single_unix_specification/events.php\n\n 	\n\n** All cal
 ls are anchored on US time **\n\nTopic: Austin Group teleconference\n-
 --\nAudio conference infor
 mation\n---\n\nYou are
  invited to a Zoom meeting.\n\nMeeting ID: 618 156 403\n\nJoin from PC\, M
 ac\, iOS or Android: https://logitech.zoom.us/j/618156403\n \nor join by p
 hone:\nUS: 888 974 9888\nUK: 800 031 5717\nDE: 800 724 3138\nFR: 805 082 5
 88\n\nOther international numbers available here:\nhttps://zoom.us/u/adlvr
 b8ILj\n \nMeeting ID: 618 156 403\n\nor join from a H.323/SIP Device:
 \nDial: 162.255.37.11 (US West) or 162.255.36.11 (US East)\nMeetin
 g ID: 618 156 403\n\nShare from a PC or MAC: https://zoom.us/share/6181564
 03\n\nOr iPhone one-tap (US Toll):  +16699006833\,618156403# or +164655886
 56\,618156403#\n\nAll Austin Group participants are most welcome to join t
 he call.\nThe call will last for 90 minutes.\n\n\nAn etherpad is usually u
 p for a meeting\, with a URL using the date format as below:\n\nhttp://pos
 ix.rhansen.org/p/201x-mm-dd\nusername=posix password=2115756#\n\nBug repor
 ts are available at:\nhttp://www.austingroupbugs.net\n
DTSTART;TZID=America/New_York:20200109T11
DURATION:PT1H30M0S
LAST-MODIFIED:20191220T125352Z
ORGANIZER;CN=Single UNIX Specification:MAILTO:do-not-re...@opengroup.org
SEQUENCE:0
STATUS:CONFIRMED
SUMMARY:Austin Group teleconference +1 888 974 9888 PIN 618 156 403
TRANSP:OPAQUE
URL:https://collaboration.opengroup.org/platform/single_unix_specification/
 events.php
X-MICROSOFT-CDO-ALLDAYEVENT:FALSE
X-VISIBILITY:40
X-JOINBEFORE:5
X-CATEGORY:Teleconference
X-PLATO-SITE:Single UNIX Specification
X-PLATO-SITEID:136
END:VEVENT
END:VCALENDAR


meeting.ics
Description: application/ics


Minutes of the 19th December 2019 Teleconference

2019-12-20 Thread Andrew Josey
All
Enclosed are the minutes from our last call this year. Happy Holidays!
regards
Andrew
---

Minutes of the 19th December 2019 Teleconference Austin-993 Page 1 of 1
Submitted by Andrew Josey, The Open Group. 20th December 2019

Attendees:

Mark Ziegast, SHware Systems Dev.
Don Cragun, IEEE PASC OR
Joerg Schilling, FOKUS Fraunhofer
Andreas Grapentin, HPI, University of Potsdam
Eric Ackermann, HPI, University of Potsdam
Nick Stoughton, USENIX, ISO/IEC JTC 1/SC 22 OR
Geoff Clare, The Open Group
Andrew Josey, The Open Group

* General news 

This was the last meeting for this year. Happy Holidays to all!


* Outstanding actions

(Please note that this section has been flushed to shorten the minutes -
to locate the previous set of outstanding actions, look to the minutes
from 13th June 2019 and earlier)

Bug 1254: "asynchronous list" description uses "command" instead of "AND-OR 
list" OPEN
http://austingroupbugs.net/view.php?id=1254
Action: Joerg to investigate how his shell behaves.

Bug 700 - Nick to raise this issue with the C committee
Bug 713 - Nick to raise with the C committee.
Bug 739 - Nick to raise with the C committee.
Bug 1216 - Eric to ask if The Open Group is willing to sponsor this interface, 
referencing bug note 4478.


* Current Business


Bug 1298: ed CONSEQUENCES OF ERRORS unclear about diagnostic message Accepted
http://austingroupbugs.net/view.php?id=1298

This bug was re-opened to look at bugs 606 and 1290.

606 was closed as a duplicate of bug 0001290 since, although it
predates that bug, 1290 is tagged tc3-2008 whereas this was originally
tagged issue8.

The relationship on 1290 was replaced to note the duplicate.


Bug 1300: clarify GLOB_MARK behavior Accepted as Marked
http://austingroupbugs.net/view.php?id=1300

This item is tagged for Issue 8.

An interpretation is required (which also impacts bug 1301).
 

Note that the changes specified below address the issues raised in
this bug report and in 0001301.

Interpretation response:
The standard states "Each pathname that is a directory that matches
pattern shall have a  appended.", and conforming implementations
must conform to this. However, concerns have been raised about this
which are being referred to the sponsor.

Rationale:
Requiring the pathname "/" to be converted to "//" and the pathname
"//" to be converted to "///" was not considered when this issue
was first standardized.

Notes to the Editor (not part of this interpretation):
On page 1109 line 37544 section glob(), change:
Each pathname that is a directory that matches pattern shall
have a  appended.
to:
For each pathname that matches pattern and is determined to be
a directory after pathname resolution, process the pathname so
the result is as if the following steps are applied in order:
 
If the pathame is , do not modify the pathname and
skip the remaining steps.
 
If the pathname is  and the implementation
handles pathname resolution of a pathname starting with
exactly two successive  characters differently than
it handles a pathname starting with only a single ,
do not modify the pathname and skip the remaining steps.
 
If the pathname does not end with a , append a 
to the pathname and skip the remaining steps.

A  may be appended to the pathname.
 
If there are multiple  characters at the end of the
pathname, all but one of those trailing  characters
may be removed from the pathname.

Append the following new paragraphs to the glob() rationale after
P1112, L37648:
Earlier versions of this standard defined the behavior associated
with the flag GLOB_MARK as:

Each pathname that is a directory that matches pattern shall
have a  appended.

This was undesirable if the matched pathname was  or if
the matched pathname was  and the implementation
treats a leading  differently than it treats a
pathname with a single leading . Only a few implementations
were known to conform to this requirement (maybe only one) and
there was a lot of variation in the way other implementations
behaved. The current wording allows many of the alternative
behaviors that were observed, except that the pathnames "/" and
"//" (if it is treated differently than "/") must not be modified.

Implementations should consider the following much simpler
requirement (which is allowed by the current standard) when
processing the GLOB_MARK flag:

Each pathname that matches pattern, is determined to be a
directory after pathname resolution, and does not end with
a  shall have a  appended.


Bug 1301: clarify glob("/", GLOB_MARK, ...) behavior Accepted as marked.
http://austingroupbugs.net/view.php?id=1301

(see 1300)


Next Steps 
--

Apologies in advance:
Geoff Clare 2020-01-06, 2020

Re: system() and pthread_atfork()

2019-12-20 Thread Karstens, Nate
Thanks to everyone for the great responses! Below are some notes/discussion on 
the various replies I've seen:

> If it's supposed to behave as if fork() has been called, this implicitly 
> includes calling atfork handlers when POSIX_C_SOURCE is defined...

Regarding glibc, I'm not sure the POSIX_C_SOURCE macro would control that. Here 
is a reference to the latest definition of system() in the POSIX standard:

https://pubs.opengroup.org/onlinepubs/9699919799/functions/system.html

The glibc developers had a discussion on this topic here:

https://sourceware.org/bugzilla/show_bug.cgi?id=17490

They seemed to go back and forth on this same issue, and one developer 
suggested communicating the ambiguity with the Austin Group. I'm not sure if 
this was ever done, but there still appears to be a discrepancy (in system(), 
popen() -- 
https://pubs.opengroup.org/onlinepubs/9699919799/functions/popen.html, and 
maybe others).

> Couldn't that be addressed by SO_REUSEADDR?

According to 
https://pubs.opengroup.org/onlinepubs/9699919799/functions/V2_chap02.html#tag_15_10_16,
 SO_REUSEADDR "indicates that the rules used in validating addresses supplied 
in a https://pubs.opengroup.org/onlinepubs/9699919799/functions/bind.html 
should allow reuse of local addresses". Based on this, it doesn't appear to be 
for the purposes of addressing this issue, and we're not excited about the 
other side effects as well.

> The reason it likely that the implementer of system() and popen() get the 
> freedom to use a more efficient mechanism.

That might be, but it would be good to document the tradeoffs associated with 
that efficiency. Even better would be to come up with a mechanism to avoid it 
entirely. If requiring pthread_atfork() handlers to execute is not an option, 
then maybe a file-descriptor/socket option that marks the socket as closing 
once the process forks (like SOCK_CLOEXEC / FD_CLOEXEC, but done at fork() 
instead of exec()).

> The vfork() used before also did not call the pthread_atfork() handlers 
> either.

https://pubs.opengroup.org/onlinepubs/009604599/functions/vfork.html comes with 
a lot of warnings, an explicit recommendation to use fork(), and a note that it 
may be withdrawn in the future. As such we weren't as worried about it, but 
maybe we should be...

> If you have control over the callers of system()

We don't have control over them, which makes this more disconcerting.

Cheers,

Nate



CONFIDENTIALITY NOTICE: This email and any attachments are for the sole use of 
the intended recipient(s) and contain information that may be Garmin 
confidential and/or Garmin legally privileged. If you have received this email 
in error, please notify the sender by reply email and delete the message. Any 
disclosure, copying, distribution or use of this communication (including 
attachments) by someone other than the intended recipient is prohibited. Thank 
you.