This form contains a series of questions that need to be answered. As you go about answering the questions, please keep the following things in mind:

• While it is not required that each question be answered at this time, all questions must have answers before the response is submitted to The Open Group for review and publication.
• Press the "Save" button at any time to save work in progress. Once the work has been saved, there is the option to continue editing if required.
• Many questions have instructions to assist in development of answers. They are marked with the indicator. Please look at the instructions carefully.
• Although HTML markup can be included in answers, this is not recommended apart from basic tags such as <p> and <br>, since incorrect markup could effect the format of other items in the document.
• Questions on this system should be addressed to the Conformance Statement manager at The Open Group.

Enter the name of the Organization that produced the implementation and the name of the author of the Conformance Statement.

1. Commands and Utilities

Product Information

Environment Specification

Answer the questions for each binary-compatible family. Alternately, provide the answers in the Appendix at the end of this document.

	Testing Environment	Binary-compatible Family	Portability Environment	Indicator of Compliance	Compliance Details
			Select from this list Internationalised System Calls and Libraries Internationalised System Calls and Libraries	None.	None.
			Select from this list Internationalised System Calls and Libraries Internationalised System Calls and Libraries	None.	None.
			Select from this list Internationalised System Calls and Libraries Internationalised System Calls and Libraries	None.	None.
			Select from this list Internationalised System Calls and Libraries Internationalised System Calls and Libraries	None.	None.
			Select from this list Internationalised System Calls and Libraries Internationalised System Calls and Libraries	None.	None.

Temporary Waivers

1.1 Choice of Conformance Specification

Question 1: Which specification are you using as a basis for listing any deviant behaviour of the product?

Response

This Conformance Statement lists, in the chapter entitled Commands and Utilities - Historical Compatibility, all the discrepancies between the product behaviour and that specified in X/Open Specification, Commands and Utilities, Issue 3 (C211) (formerly XSI Commands and Utilities, XO/XPG/89/002, Volume 1 of the X/Open Portability Guide, Issue 3), and X/Open Specification, Supplementary Definitions, Issue 3 (C213) (formerly XSI Supplementary Definitions, XO/XPG/89/004, Volume 3 of the X/Open Portability Guide, Issue 3), Section 18.4, cpio and Section 18.5, tar (extended tar archive file formats). If you select this option, answer only the questions in section 2 of this document - Commands and Utilities - Historical Compatibility.

This Conformance Statement lists, in the chapter entitled Commands and Utilities - POSIX Compatibility, all the discrepancies between the product behaviour and that specified in CAE Specification, Commands and Utilities, Issue 4 (C203) and CAE Specification, System Interface Definitions, Issue 4 (C204). If you select this option, answer only the questions in section 3 of this document - Commands and Utilities - POSIX Compatibility.

Rationale

The Commands and Utilities Product Standard Definition requires that the discrepancies between product behaviour and either of the two specifications shown above be documented.

Reference

Component Definitions, Version 1 (July 1992), Part 2 of X/Open Systems and Branded Products: XPG4, Section 3.2, XPG4 Commands and Utilities.

2.1 Basic Utilities

2.1.1 Supported Commands

Question 1: Which of the basic utilities (non-development utilities) defined in XPG3, Volume 1 are not provided with the implementation?

Response

Rationale

XPG3, Volume 1 states that ``This volume in its current form is useful only as a guide to portability, but it is not possible to precisely define or test conformance to it.''. This question determines whether or not the implementation provides a command of the name specified in XPG3; it does not attempt to determine whether it supports the semantics of that command. The optional development utilities are excluded from this question and are dealt with in the next section of the questionnaire.

Example:

The mailx and newgrp commands are not provided.

Reference

X/Open Portability Guide, Issue 3, Volume 1, Commands and Utilities, Chapter 1, Introduction.

2.1.2 Command Behaviour

Question 2: In what ways do the commands provided by the implementation behave differently from that specified in XPG3?

Response

The commands behave in the manner specified for each of the command options detailed in XPG3.

A list of deviances for each of the commands is provided.



	Utility Name	Option	Description

Rationale

This question provides a greater degree of granularity than the previous question, requiring the semantic differences associated with the commands to be specified. Again, the question relates to the basic utilities rather than the development utilities. The question only relates to the semantics of the options specified within XPG3; implementation-specific extensions should not be documented.

Reference

X/Open Portability Guide, Issue 3, Volume 1, Commands and Utilities, Chapter 1, Introduction.

2.2 Development Utilities

2.2.1 Supported Commands

Question 3: Which of the development utilities defined in XPG3 are not provided with the implementation?

Response

Specify either "All are provided.", "None are provided.", or provide a list of utilities that are not provided in the area below.

Rationale

XPG3, Volume 1 states that ``The development utilities might not be present in all X/Open-compliant systems; in designated (DEVELOPMENT) systems all of the development utilities must be present and must conform to the published definition.''.

Reference

X/Open Portability Guide, Issue 3, Volume 1, Commands and Utilities, Section 1.2.3, Development.

2.2.2 Command Behaviour

Question 4: In what ways do the development utilities provided by the implementation behave differently from the specifications contained in XPG3?

Response

The development utilities behave in the manner specified for each of the options detailed in XPG3.

A list of deviances for each of the utilities is provided.



	Utility Name	Option	Description

Rationale

This question provides a greater degree of granularity than the previous question, requiring the semantic differences associated with the development utilities to be specified. The question only relates to the semantics of the options specified within XPG3; implementation-specific extensions should not be documented.

Reference

X/Open Portability Guide, Issue 3, Volume 1, Commands and Utilities, Section 1.2.3, Development.

2.3 Internationalisation Option

2.3.1 Commands and Utilities

Question 5: Is an internationalised environment, reflecting changes in the locale setting as described in XPG3, Volume 1, Commands and Utilities, supported?

Response

The commands listed below support internationalisation in the manner specified in XPG3. Any deviations in the internationalised behaviour of the following commands compared to that specified in XPG3 are marked ``No'' and further description of the deviation is provided.

Command	Behaviour Specified in XPG3	Supported	Description
ar	LC_TIME affects date format.	Yes   No
awk	LC_COLLATE, LC_CTYPE affect regular expression matching.	Yes   No
	LC_COLLATE affects the behaviour of string comparisons.	Yes   No
	LC_NUMERIC affects the behaviour of the radix character.	Yes   No
comm	LC_COLLATE affects sorting sequence.	Yes   No
cp,ln,mv	LANG affects yes string.	Yes   No
cpio	LC_COLLATE, LC_CTYPE affect filename pattern matching.	Yes   No
	LC_TIME affects date format.	Yes   No
date	LC_TIME affects date formatting options.	Yes   No
ed,red	LC_COLLATE, LC_CTYPE affect regular expression matching.	Yes   No
	LC_CTYPE is used to determine whether characters are printable.	Yes   No
egrep	LC_COLLATE, LC_CTYPE affect regular expression matching.	Yes   No
	LC_CTYPE is used to determine character classification (alphabetic, upper-case, lower-case).	Yes   No
expr	LC_COLLATE, LC_CTYPE affect regular expression matching.	Yes   No
	LC_COLLATE affects the behaviour of relational operators.	Yes   No
fgrep	LC_CTYPE is used to determine character classification (alphabetic, upper-case, lower-case).	Yes   No
find	LANG affects yes string.	Yes   No
	LC_COLLATE, LC_CTYPE affect filename pattern matching.	Yes   No
grep	LC_COLLATE, LC_CTYPE affect regular expression matching.	Yes   No
	LC_CTYPE is used to determine character classification (alphabetic, upper-case, lower-case).	Yes   No
join	LC_COLLATE affects sorting sequence.	Yes   No
lpstat	LC_TIME affects date format.	Yes   No
ls	LC_COLLATE affects sorting sequence.	Yes   No
	LC_CTYPE is used to determine whether a character is printable.	Yes   No
	LC_TIME affects date format.	Yes   No
mail	LC_TIME affects date format.	Yes   No
mailx	LC_COLLATE, LC_CTYPE affect filename pattern matching.	Yes   No
	LC_TIME affects date format.	Yes   No
pg	LC_COLLATE, LC_CTYPE affect filename pattern matching.	Yes   No
pr	LC_TIME affects date format.	Yes   No
	LC_CTYPE is used to determine whether a character is printable.	Yes   No
ps	LC_TIME affects date format.	Yes   No
rm,rmdir	LANG affects yes string.	Yes   No
sed	LC_COLLATE, LC_CTYPE affect regular expression matching.	Yes   No
	LC_CTYPE is used to determine whether a character is printable.	Yes   No
sh	LC_COLLATE, LC_CTYPE affect filename pattern matching.	Yes   No
	LC_CTYPE is used to determine whether a character is alphabetic.	Yes   No
sort	LC_COLLATE affects sorting sequence.	Yes   No
	LC_CTYPE affects character classification (alphabetic, upper-case, printing).	Yes   No
	LC_NUMERIC affects the determination of the radix character.	Yes   No
tar	LC_TIME affects date format.	Yes   No
	LANG affects yes string.	Yes   No
tr	LC_COLLATE, LC_CTYPE affect bracketed expressions.	Yes   No
	LC_CTYPE affects the definition of the character universe.	Yes   No
uniq	LC_COLLATE affects sorting sequence.	Yes   No
uucp	LC_TIME affects date format.	Yes   No
uustat	LC_TIME affects date format.	Yes   No
wc	LC_CTYPE is used to determine white-space characters.	Yes   No
who	LC_TIME affects date format.	Yes   No
yacc	LC_CTYPE is used to determine character classification.	Yes   No

Rationale

This behaviour is intended to be collectively optional; that is, it should be provided for all commands listed (subject to Sections 3.1 and 3.2 which identify those commands not supplied by the vendor and those that do not fully support the X/Open Specification).

Reference

X/Open Portability Guide, Issue 3, Volume 1, Commands and Utilities, Chapter 2, Status of Interfaces.

2.3.2 Regular Expressions in Commands

Question 6: Which form of regular expression syntax is supported by those commands that use regular expressions?

Response

Note: An XPG3 conforming system that claims support for internationalised commands should in no case provide the regular expression syntax marked with an asterisk in the table below.

Command	Regular Expression Syntax Supported
awk	Extended*   Extended Internationalised
csplit	Simple   Simple Internationalised
ed	Simple*   Simple Internationalised
egrep	Extended*   Extended Internationalised
ex	Simple   Simple Internationalised
expr	Simple*   Simple Internationalised
grep	Simple*   Simple Internationalised
lex	Extended   Extended Internationalised
pg	Simple*   Simple Internationalised
sdb	Simple   Simple Internationalised
sed	Simple*   Simple Internationalised
vi	Simple   Simple Internationalised

Rationale

XPG3, Volume 3, XSI Supplementary Definitions requires that an internationalised set of commands will provide regular expression syntax for the above commands in one of the forms specified for that command. XPG3 encourages the implementation of internationalised regular expressions for all of the above utilities. It should be noted that the sdb command is an optional development utility and may not be available on all XSI-conformant systems.

Reference

X/Open Portability Guide, Issue 3, Volume 3, Supplementary Definitions, Chapter 6, Regular Expressions.

3.1 Basic Utilities

3.1.1 Supported Commands

Question 1: Which of the basic utilities (non-development utilities) defined in CAE Specification, Commands and Utilities, Issue 4, are not provided with the implementation?

Response

Rationale

This question determines whether or not the implementation provides a command of the name specified in CAE Specification, Commands and Utilities, Issue 4; it does not attempt to determine whether it supports the semantics of that command. The optional development utilities are excluded from this question and are dealt with in the next section of the questionnaire.

Example:

The dis command is not provided.

Reference

Component Definitions, Version 1 (July 1992), Part 2 of X/Open Systems and Branded Products: XPG4, Section 3.2, XPG4 Commands and Utilities.

3.1.2 Command Behaviour

Question 2: In what ways do the commands provided by the implementation behave differently from the specifications contained in CAE Specification, Commands and Utilities, Issue 4?

Response

The commands behave in the manner specified for each of the command options detailed in CAE Specification, Commands and Utilities, Issue 4.

A list of deviances for each of the commands is provided.



	Utility Name	Option	Description

Rationale

This question provides a greater degree of granularity than the previous question, requiring the semantic differences associated with the commands to be specified. Again, the question relates to the basic utilities rather than the development utilities. The question only relates to the semantics of the options specified within CAE Specification, Commands and Utilities, Issue 4; implementation-specific extensions should not be documented.

Reference

Component Definitions, Version 1 (July 1992), Part 2 of X/Open Systems and Branded Products: XPG4, Section 3.2, XPG4 Commands and Utilities.

3.2 Development Utilities

3.2.1 Supported Commands

Question 3: Which of the development utilities defined in this Product Standard are not provided with the implementation?

Response

Either enter "All development utilities are provided.", "None of the development utilties are provided.", or "All the development utilities except... are provided." filling in the list as appropriate.

Rationale

The development utilities are required to exist on designated DEVELOPMENT systems but may not be present on all XSI-conformant systems.

Reference

CAE Specification, Commands and Utilities, Issue 4, Section 1.3.2, Development.

3.2.2 Command Behaviour

Question 4: In what ways do the commands provided by the implementation behave differently from the specifications contained in CAE Specification, Commands and Utilities, Issue 4?

Response

The commands behave in the manner specified for each of the command options detailed in CAE Specification, Commands and Utilities, Issue 4.

A list of deviances for each of the commands is provided.



	Utility Name	Option	Description

Rationale

This question provides a greater degree of granularity than the previous question, requiring the semantic differences associated with the commands to be specified. Again, the question relates to the basic utilities rather than the development utilities. The question only relates to the semantics of the options specified within CAE Specification, Commands and Utilities, Issue 4; implementation-specific extensions should not be documented.

Reference

CAE Specification, Commands and Utilities, Issue 4, Section 1.3.2, Development.

3.3 FORTRAN Option

3.3.1 FORTRAN Utility

Question 5: Is the FORTRAN fort77 utility provided?

Response

Yes   No

Rationale

The fort77 utility is the command level interface to the FORTRAN compiler, which need not be provided.

Reference

CAE Specification, Commands and Utilities, Issue 4, Section 1.3.3, FORTRAN.

3.3.2 Command Behaviour

Question 6: In what ways does the fort77 utility provided by the implementation behave differently from the specification contained in CAE Specification, Commands and Utilities, Issue 4?

Response

The command behaves in the manner specified for each of the command options detailed in CAE Specification, Commands and Utilities, Issue 4.

A list of deviances for the command is provided.

Not applicable (the fort77 utility is not provided).



	Utility Name	Option	Description

Rationale

This question provides a greater degree of granularity than the previous question, requiring the semantic differences associated with the command to be specified. Again, the question relates to the basic utilities rather than the development utilities. The question only relates to the semantics of the options specified within CAE Specification, Commands and Utilities, Issue 4; implementation-specific extensions should not be documented.

Reference

CAE Specification, Commands and Utilities, Issue 4, Section 1.3.3, FORTRAN.

3.4 Possibly Unsupportable Utilities and Options

Question 7: Which of the following utilities and utility options are not supported on the implementation?

Response

Utility	Option	Supported
ar	-s	Supported   Unsupported
cancel		Supported   Unsupported
cu		Supported   Unsupported
lp	-m	Supported   Unsupported
lp	-o	Supported   Unsupported
lp	-t	Supported   Unsupported
lp	-w	Supported   Unsupported
lpstat		Supported   Unsupported
sort	-z	Supported   Unsupported
tabs	+m	Supported   Unsupported
uucp		Supported   Unsupported
uulog		Supported   Unsupported
uuname		Supported   Unsupported
uupick		Supported   Unsupported
uustat		Supported   Unsupported
uuto		Supported   Unsupported
uux		Supported   Unsupported

Rationale

A number of utilities and utility options are marked as possibly unsupportable features, and the functionality associated with these need not be present in a conforming implementation.

Reference

CAE Specification, Commands and Utilities, Issue 4, Section 1.7, Portability.

3.5 Specific Commands and Utilities

3.5.1 at

Question 8: How does the at command interpret a non-null SHELL environment variable?

Response

Uses the shell specified in the SHELL environment variable. Uses the login shell from the user database. Uses sh irrespective of the setting of SHELL.

Rationale

The interpretation of the SHELL environment variable can cause at to invoke different versions of the shell on some implementations.

Reference

CAE Specification, Commands and Utilities, Issue 4, Chapter 3, Utilities, at, ENVIRONMENT VARIABLES, SHELL.

Question 9: What is the limit on the number of open streams provided by awk?

Response

open streams.

Rationale

The number of open streams that are available to awk may differ between implementations, possibly depending on the number of streams that are available to a process ({FOPEN_MAX}).

Reference

CAE Specification, Commands and Utilities, Issue 4, Chapter 3, Utilities, awk, Input/Output and General Functions, close().

3.5.2 batch

Question 10: How does the batch command interpret a non-null SHELL environment variable?

Response

Uses the shell specified in the SHELL environment variable. Uses the login shell from the user database. Uses sh irrespective of the setting of SHELL.

Rationale

The interpretation of the SHELL environment variable can cause batch to invoke different versions of the shell on some implementations.

Reference

CAE Specification, Commands and Utilities, Issue 4, Chapter 3, Utilities, batch, ENVIRONMENT VARIABLES, SHELL.

Question 11: Which defined names are automatically provided by the compiler?

Response

Rationale

The automatic provision of defined names by the compiler can cause these names to be unavailable in the name space for defined names.

Reference

CAE Specification, Commands and Utilities, Issue 4, Chapter 3, Utilities, c89, OPTIONS, -D.

Question 12: When multiple input files are specified, where does c89 direct identification messages designating the start of each input file processing?

Response

Standard output. Standard error. These messages are not generated.

Rationale

These messages, if produced, must be written to one or the other of standard output and standard error, but not to both. The destination of these messages is useful in determining redirections that are necessary to identify the input files from which warning messages are generated.

Reference

CAE Specification, Commands and Utilities, Issue 4, Chapter 3, Utilities, c89, STDOUT and STDERR.

Question 13: What are the limits associated with external symbols imposed by c89?

Response

Description	Minimum Maximum	Implementation Maximum
Number of significant bytes	31
Number of source or object files	511
Total number of external symbols	4095

Rationale

These limits vary between implementations and cannot be reset by the user. The XCU definition gives the minimum maximum value for each of the values. Some applications may require larger limits than these minimum maxima.

Reference

CAE Specification, Commands and Utilities, Issue 4, Chapter 3, Utilities, c89, EXTENDED DESCRIPTION, External Symbols.

3.5.3 cancel

Question 14: Is the submitter of an lp job notified when the job is cancelled by someone else?

Response

Yes   No

Rationale

It is useful for the submitter of a job to be notified of its cancellation, rather than having to interrogate the line printer queue to obtain this information.

Reference

CAE Specification, Commands and Utilities, Issue 4, Chapter 3, Utilities, cancel, ENVIRONMENT VARIABLES, LANG.

3.5.4 cp

Question 15: What is the affect of alternate access control mechanisms on file copies?

Response

Either ented "No alternate access control mechanisms are implemented." or provide a description of the effect of these controls on file copying, or an indication of where it is documented.

Rationale

Because of the additional restrictions on creating files and reading data from files, the cp utility may not behave as described when alternate access control mechanisms are in use.

Reference

CAE Specification, Commands and Utilities, Issue 4, Chapter 3, Utilities, cp, DESCRIPTION, final paragraph.

3.5.5 date

Question 16: Does date permit the setting of the date and time?

Response

Yes   No

Rationale

Some systems, particularly those that are hosted as part of a total system environment, do not allow the date command to set the date. On such systems, the setting of the date can only be accomplished from the host environment.

Reference

CAE Specification, Commands and Utilities, Issue 4, Chapter 3, Utilities, date, OPERANDS, mmddhhmm[yy].

3.5.6 ex

Question 17: What restrictions are imposed on the set of commands within the rhs of the map command?

Response

Either enter "None." or a list of restrictions, or a reference to your system documentation where these restrictions are described.

Rationale

Implementations may impose restrictions on the commands that can be used by macros in visual mode.

Reference

CAE Specifications, Commands and Utilities, Issue 4, Chapter 3, Utilities, ex, EXTENDED DESCRIPTION, Command Descriptions in ex, Map.

3.5.7 fc

Question 18: Is the history list mechanism disabled for users with appropriate privileges who do not set HISTFILE?

Response

Yes   No

Rationale

This Product Standard states that an implementation may, in certain circumstances, disable the history list mechanism for users with appropriate privileges who do not set HISTFILE. This could have some security implications.

Reference

CAE Specification, Commands and Utilities, Issue 4, Chapter 3, Utilities, fc, ENVIRONMENT VARIABLES, HISTFILE.

3.5.8 fort77

Question 19: When multiple input files are specified, where does fort77 direct identification messages designating the start of each input file processing?

Response

Not applicable. Standard output. Standard error. These messages are not generated.

Rationale

These messages, if produced, must be written to one or the other of standard output and standard error, but not to both. The destination of these messages is useful in determining redirections that are necessary to identify the input files from which warning messages are generated.

Reference

CAE Specification, Commands and Utilities, Issue 4, Chapter 3, Utilities, fort77, STDERR.

Question 20: What are the limits associated with external symbols imposed by fort77?

Response

Description	Minimum Maximum	Implementation Maximum
Number of significant bytes	31
Number of source or object files	511
Total number of external symbols	4095

Rationale

These limits vary between implementations and cannot be reset by the user. The XCU definition gives the minimum maximum value for each of the values. Some applications may require larger limits than these minimum maxima.

Reference

CAE Specification, Commands and Utilities, Issue 4, Chapter 3, Utilities, fort77, EXTENDED DESCRIPTION, External Symbols.

3.5.9 lex

Question 21: Where are error messages sent when the lex -t option is not specified?

Response

Standard output. Standard error.

Rationale

These messages can be directed to either standard output or standard error according to this Product Standard, though the messages are not allowed to be directed to both. An application may wish to redirect these messages to a file.

Reference

CAE Specification, Commands and Utilities, Issue 4, Chapter 3, Utilities, lex, STDOUT.

3.5.10 ln

Question 22: Can ln create links to a directory?

Response

Yes   No

Rationale

Implementations may disallow the creation of hard links to a directory, even though the executing process has the appropriate privileges.

Reference

CAE Specification, Commands and Utilities, Issue 4, Chapter 3, Utilities, ln, OPERANDS, source_file.

3.5.11 localedef

Question 23: What is the default character mapping used when the localedef -f option is not specified?

Response

Either enter the name of the default character mapping used by localedef, or alternatively provide a reference to your system documentation where this character mapping file is described.

Rationale

This Product Standard does not define a specific character mapping as the default for conforming systems. This character mapping provides encoding information for the members of the portable character set required by this Product Standard.

Reference

CAE Specification, Commands and Utilities, Issue 4, Chapter 3, Utilities, localedef, OPTIONS, -f.

3.5.12 lp

Question 24: What lp option or operator command is used to suppress the printing of a banner page?

Response

Rationale

The user may require that banner pages are suppressed in cases where pre-printed forms are used and the stationary is of a non-standard length.

Reference

CAE Specification, Commands and Utilities, Issue 4, Chapter 3, Utilities, lp, DESCRIPTION.

3.5.13 ls

Question 25: How many bytes are in a block as reported by ls?

Response

bytes in a block.

Rationale

The block size used by ls to report the number of blocks occupied by a file varies from system to system; often this depends on the underlying file system architecture.

Reference

CAE Specification, Commands and Utilities, Issue 4, Chapter 3, Utilities, ls, OPTIONS, -s.

3.5.14 make

Question 26: What additional variables does make add to its environment?

Response

Rationale

The implementation of make may set certain environment variables on invocation of make. These variables may not be set by the user, thus reducing the name space for environment variables.

Reference

CAE Specification, Commands and Utilities, Issue 4, Chapter 3, Utilities, make, EXTENDED DESCRIPTION, Makefile Execution.

Question 27: Does the default MAKEFLAGS environment variable contain additional implementation-dependent options?

Response

Rationale

The implementation of make may set certain default MAKEFLAGS options on invocation of make. These variables are in addition to those set by the user on the command line and could affect the processing of make.

Reference

CAE Specification, Commands and Utilities, Issue 4, Chapter 3, Utilities, make, EXTENDED DESCRIPTION, Makefile Execution.

3.5.15 newgrp

Question 28: Does newgrp allow users who are not listed as a member of a group which has no password to change to that group?

Response

Yes   No

Rationale

On some implementations, a user who is not listed as a member of a group may change to that group in the case that there is no password associated with the group.

Reference

CAE Specification, Commands and Utilities, Issue 4, Chapter 3, Utilities, newgrp, DESCRIPTION.

Question 29: Are there any other implementation-specific authorisation restrictions that affect newgrp?

Response

Rationale

Some implementations may impose accounting or other restrictions that could cause newgrp to deny activity to a group member. For example, a resource quota system could be implemented on a group basis that would limit the ability to join a group until the resources were available to the group.

Reference

CAE Specification, Commands and Utilities, Issue 4, Chapter 3, Utilities, newgrp, DESCRIPTION.

3.5.16 nice and renice

Question 30: What are the limits and default values used by nice and renice?

Response

Maximum nice value is .
Minimum nice value is .
Default nice increment is .

Rationale

Each of these values differs between implementations and the range of values gives the user some control over the relative priority of processes.

Reference

CAE Specification, Commands and Utilities, Issue 4, Chapter 3, Utilities, nice, DESCRIPTION.

3.5.17 pax

Question 31: What is the default archive format used by pax?

Response

If your default format is implementation-dependent, place a description of the format in the box below. Otherwise, enter "Extended tar." or "Extended cpio."

Rationale

The implementation has the choice as to which format it shall use as the default when it is creating files. When it is reading an archive created in either extended tar or extended cpio format (or any other format that it understands), the pax utility will read the archive in the format as written.

Reference

CAE Specification, Commands and Utilities, Issue 4, Chapter 3, Utilities, pax, DESCRIPTION.

Question 32: How does pax handle reading and writing of archives that span multiple files?

Response

Provide a description of how pax reads and writes archives that exceed the size of the output/input media. Alternatively specify where it is documented.

Rationale

In many cases pax will take actions, such as prompting the user for the device name to use for the next archive file, when the current archive file is full. There may be extensions to the syntax of pax which allow the user to specify the address to use to access subsequent files.

Reference

CAE Specification, Commands and Utilities, Issue 4, Chapter 3, Utilities, pax, DESCRIPTION.

Question 33: How does pax handle invalid filenames when it is extracting files from an archive?

Response

Provide a description of how pax handles invalid filenames on extraction, detailing the type of error message produced or the algorithm used to generate a filename. Alternatively specify where it is documented.

Rationale

An implementation may either extract the data associated with these files into files named in an implementation-defined manner or may issue an error indicating that the file is being ignored. If pax extracts the file, it is necessary for the user either to be informed of the file that is used or to know the algorithm that pax uses in generating these filenames.

Reference

CAE Specification, Commands and Utilities, Issue 4, Chapter 3, Utilities, pax, EXTENDED DESCRIPTION, The cpio Filename.

3.5.18 printf

Question 34: Does printf support the e, E, f, g and G floating point conversion specifications?

Response

Yes   No

Rationale

The support of these conversions is not required on an XCU conforming system.

Reference

CAE Specification, Commands and Utilities, Issue 4, Chapter 3, Utilities, printf, EXAMPLES.

3.5.19 sh

Question 35: Is the environment variable IFS ignored when the shell is invoked?

Response

Yes   No

Rationale

The XCU definition allows that the sh command ignore the setting of the IFS environment variable on invocation. The setting of this variable has been used to breach security on systems which use the shell to interpret a call to the system() and execvp() interfaces.

Reference

CAE Specification, Commands and Utilities, Issue 4, Chapter 3, Utilities, sh, ENVIRONMENT VARIABLES, IFS.

3.5.20 touch

Question 36: What is the latest date after the Epoch that can be used by touch?

Response

Rationale

Because of the limitations on the storage of times in the stat structure associated with a file, there is a limitation on the valid dates that can be specified to touch. This is directly related to the value that can be stored in the integral type time_t.

Reference

CAE Specification, Commands and Utilities, Issue 4, Chapter 3, Utilities, touch, OPTIONS, -t.

3.5.21 yacc

Question 37: What are the limits of yacc's internal tables?

Response

Description	Minimum Maximum	Implementation Maximum
Number of tokens	126
Number of non-terminals	200
Number of rules	300
Number of states	600
Length of rules	5200
Number of actions	4000

Rationale

These internal table sizes vary between implementations and cannot be reset by the user. The XCU definition gives the minimum maximum value for each of the table values.

Reference

CAE Specification, Commands and Utilities, Issue 4, Chapter 3, Utilities, yacc, EXTENDED DESCRIPTION, Limits.

4. Appendix

Copyright © 
All rights reserved.

5. Change History