Un outil pour savoir si une commande est posix - retour accueil
git clone git://bebou.netlib.re/isposix
Log | Files | Refs | README |
admin.html (23915B)
1 <!-- Copyright 2001-2024 IEEE and The Open Group, All Rights Reserved -->
2 <!DOCTYPE HTML>
3 <html lang="en">
4 <head>
5 <meta name="generator" content="HTML Tidy for HTML5 for Linux version 5.8.0">
6 <meta http-equiv="Content-Type" content="text/html; charset=utf-8">
7 <link type="text/css" rel="stylesheet" href="style.css"><!-- Generated by The Open Group rhtm tool v1.2.4 -->
8 <!-- Copyright (c) 2001-2024 The Open Group, All Rights Reserved -->
9 <title>admin</title>
10 </head>
11 <body bgcolor="white">
12 <div class="NAVHEADER">
13 <table summary="Header navigation table" class="nav" width="100%" border="0" cellpadding="0" cellspacing="0">
14 <tr class="nav">
15 <td class="nav" width="15%" align="left" valign="bottom"><a href="../utilities/V3_chap03.html" accesskey="P"><<<
16 Previous</a></td>
17 <td class="nav" width="70%" align="center" valign="bottom"><a href="contents.html">Home</a></td>
18 <td class="nav" width="15%" align="right" valign="bottom"><a href="../utilities/alias.html" accesskey="N">Next
19 >>></a></td>
20 </tr>
21 </table>
22 <hr align="left" width="100%"></div>
23 <script language="JavaScript" src="../jscript/codes.js"></script><basefont size="3">
24 <center><font size="2">The Open Group Base Specifications Issue 8<br>
25 IEEE Std 1003.1-2024<br>
26 Copyright © 2001-2024 The IEEE and The Open Group</font></center>
27 <hr size="2" noshade>
28 <a name="top" id="top"></a> <a name="admin" id="admin"></a> <a name="tag_20_01" id="tag_20_01"></a><!-- admin -->
29 <h4 class="mansect"><a name="tag_20_01_01" id="tag_20_01_01"></a>NAME</h4>
30 <blockquote>admin — create and administer SCCS files (<b>DEVELOPMENT</b>)</blockquote>
31 <h4 class="mansect"><a name="tag_20_01_02" id="tag_20_01_02"></a>SYNOPSIS</h4>
32 <blockquote class="synopsis">
33 <div class="box"><code><tt><sup>[<a href="javascript:open_code('XSI')">XSI</a>]</sup> <img src="../images/opt-start.gif" alt=
34 "[Option Start]" border="0"> admin -i</tt><b>[</b><i>name</i><b>] [</b><tt>-n</tt><b>] [</b><tt>-a</tt> <i>login</i><b>]
35 [</b><tt>-d</tt> <i>flag</i><b>] [</b><tt>-e</tt> <i>login</i><b>] [</b><tt>-f</tt> <i>flag</i><b>]<br></b>
36 <tt> </tt> <b>[</b><tt>-m</tt> <i>mrlist</i><b>] [</b><tt>-r</tt> <i>rel</i><b>]
37 [</b><tt>-t</tt><b>[</b><i>name</i><b>] [</b><tt>-y</tt><b>[</b><i>comment</i><b>]]</b> <i>newfile</i> <tt><br>
38 <br>
39 admin -n</tt> <b>[</b><tt>-a</tt> <i>login</i><b>] [</b><tt>-d</tt> <i>flag</i><b>] [</b><tt>-e</tt> <i>login</i><b>]
40 [</b><tt>-f</tt> <i>flag</i><b>] [</b><tt>-m</tt> <i>mrlist</i><b>]<br></b> <tt> </tt>
41 <b>[</b><tt>-t</tt><b>[</b><i>name</i><b>]] [</b><tt>-y</tt><b>[</b><i>comment</i><b>]]</b> <i>newfile</i><tt>...<br>
42 <br>
43 admin</tt> <b>[</b><tt>-a</tt> <i>login</i><b>] [</b><tt>-d</tt> <i>flag</i><b>] [</b><tt>-m</tt> <i>mrlist</i><b>]
44 [</b><tt>-r</tt> <i>rel</i><b>] [</b><tt>-t</tt><b>[</b><i>name</i><b>]]</b> <i>file</i><tt>...<br>
45 <br>
46 admin -h</tt> <i>file</i><tt>...<br>
47 <br>
48 admin -z</tt> <i>file</i><tt>... <img src="../images/opt-end.gif" alt="[Option End]" border="0"></tt></code></div>
49 <tt><br></tt></blockquote>
50 <h4 class="mansect"><a name="tag_20_01_03" id="tag_20_01_03"></a>DESCRIPTION</h4>
51 <blockquote>
52 <p>The <i>admin</i> utility shall create new SCCS files or change parameters of existing ones. If a named file does not exist, it
53 shall be created, and its parameters shall be initialized according to the specified options. Parameters not initialized by an
54 option shall be assigned a default value. If a named file does exist, parameters corresponding to specified options shall be
55 changed, and other parameters shall be left as is.</p>
56 <p>All SCCS filenames supplied by the application shall be of the form s.<i>filename</i>. New SCCS files shall be given read-only
57 permission mode. Write permission in the parent directory is required to create a file. All writing done by <i>admin</i> shall be
58 to a temporary <i>x-file</i>, named x.<i>filename</i> (see <a href="../utilities/get.html#"><i>get</i></a> ) created with read-only
59 mode if <i>admin</i> is creating a new SCCS file, or created with the same mode as that of the SCCS file if the file already
60 exists. After successful execution of <i>admin</i>, the SCCS file shall be removed (if it exists), and the <i>x-file</i> shall be
61 renamed with the name of the SCCS file. This ensures that changes are made to the SCCS file only if no errors occur.</p>
62 <p>The <i>admin</i> utility shall also use a transient lock file (named z.<i>filename</i>), which is used to prevent simultaneous
63 updates to the SCCS file; see <a href="../utilities/get.html#"><i>get</i></a> .</p>
64 </blockquote>
65 <h4 class="mansect"><a name="tag_20_01_04" id="tag_20_01_04"></a>OPTIONS</h4>
66 <blockquote>
67 <p>The <i>admin</i> utility shall conform to XBD <a href="../basedefs/V1_chap12.html#tag_12_02"><i>12.2 Utility Syntax
68 Guidelines</i></a> , except that the <b>-i</b>, <b>-t</b>, and <b>-y</b> options have optional option-arguments. These optional
69 option-arguments shall not be presented as separate arguments. The following options are supported:</p>
70 <dl compact>
71 <dd></dd>
72 <dt><b>-n</b></dt>
73 <dd>Create a new SCCS file. When <b>-n</b> is used without <b>-i</b>, the SCCS file shall be created with control information but
74 without any file data.</dd>
75 <dt><b>-i[</b><i>name</i><b>]</b></dt>
76 <dd>Specify the <i>name</i> of a file from which the text for a new SCCS file shall be taken. The text constitutes the first delta
77 of the file (see the <b>-r</b> option for the delta numbering scheme). If the <b>-i</b> option is used, but the <i>name</i>
78 option-argument is omitted, the text shall be obtained by reading the standard input. If this option is omitted, the SCCS file
79 shall be created with control information but without any file data. The <b>-i</b> option implies the <b>-n</b> option.</dd>
80 <dt><b>-r </b><i>SID</i></dt>
81 <dd>Specify the SID of the initial delta to be inserted. This SID shall be a trunk SID; that is, the branch and sequence numbers
82 shall be zero or missing. The level number is optional, and defaults to 1.</dd>
83 <dt><b>-t[</b><i>name</i><b>]</b></dt>
84 <dd>Specify the <i>name</i> of a file from which descriptive text for the SCCS file shall be taken. In the case of existing SCCS
85 files (neither <b>-i</b> nor <b>-n</b> is specified):
86 <ul>
87 <li>
88 <p>A <b>-t</b> option without a <i>name</i> option-argument shall cause the removal of descriptive text (if any) currently in the
89 SCCS file.</p>
90 </li>
91 <li>
92 <p>A <b>-t</b> option with a <i>name</i> option-argument shall cause the text (if any) in the named file to replace the descriptive
93 text (if any) currently in the SCCS file.</p>
94 </li>
95 </ul>
96 </dd>
97 <dt><b>-f </b><i>flag</i></dt>
98 <dd>Specify a <i>flag</i>, and, possibly, a value for the <i>flag</i>, to be placed in the SCCS file. Several <b>-f</b> options may
99 be supplied on a single <i>admin</i> command line. Implementations shall recognize the following flags and associated values:
100 <dl compact>
101 <dd></dd>
102 <dt><b>b</b></dt>
103 <dd>Allow use of the <b>-b</b> option on a <a href="../utilities/get.html"><i>get</i></a> command to create branch deltas.</dd>
104 <dt><b>c</b><i>ceil</i></dt>
105 <dd>Specify the highest release (that is, ceiling), a number less than or equal to 9999, which may be retrieved by a <a href=
106 "../utilities/get.html"><i>get</i></a> command for editing. The default value for an unspecified <b>c</b> flag shall be 9999.</dd>
107 <dt><b>f</b><i>floor</i></dt>
108 <dd>Specify the lowest release (that is, floor), a number greater than 0 but less than 9999, which may be retrieved by a <a href=
109 "../utilities/get.html"><i>get</i></a> command for editing. The default value for an unspecified <b>f</b> flag shall be 1.</dd>
110 <dt><b>d</b><i>SID</i></dt>
111 <dd>Specify the default delta number (SID) to be used by a <a href="../utilities/get.html"><i>get</i></a> command.</dd>
112 <dt><b>i</b><i>str</i></dt>
113 <dd>Treat the "No ID keywords" message issued by <a href="../utilities/get.html"><i>get</i></a> or <a href=
114 "../utilities/delta.html"><i>delta</i></a> as a fatal error. In the absence of this flag, the message is only a warning. The
115 message is issued if no SCCS identification keywords (see <a href="../utilities/get.html#"><i>get</i></a> ) are found in the text
116 retrieved or stored in the SCCS file. If a value is supplied, the application shall ensure that the keywords exactly match the
117 given string; however, the string shall contain a keyword, and no embedded <newline> characters.</dd>
118 <dt><b>j</b></dt>
119 <dd>Allow concurrent <a href="../utilities/get.html"><i>get</i></a> commands for editing on the same SID of an SCCS file. This
120 allows multiple concurrent updates to the same version of the SCCS file.</dd>
121 <dt><b>l</b><i>list</i></dt>
122 <dd>Specify a <i>list</i> of releases to which deltas can no longer be made (that is, <a href=
123 "../utilities/get.html"><i>get</i></a> <b>-e</b> against one of these locked releases fails). Conforming applications shall use the
124 following syntax to specify a <i>list</i>. Implementations may accept additional forms as an extension:
125 <pre>
126 <tt><list> ::= a | <range-list>
127 <range-list> ::= <range> | <range-list>, <range>
128 <range> ::= <SID>
129 </tt></pre>
130 <p>The character <i>a</i> in the <i>list</i> shall be equivalent to specifying all releases for the named SCCS file. The
131 non-terminal <<i>SID</i>> in range shall be the delta number of an existing delta associated with the SCCS file.</p>
132 </dd>
133 <dt><b>n</b></dt>
134 <dd>Cause <a href="../utilities/delta.html"><i>delta</i></a> to create a null delta in each of those releases (if any) being
135 skipped when a delta is made in a new release (for example, in making delta 5.1 after delta 2.7, releases 3 and 4 are skipped).
136 These null deltas shall serve as anchor points so that branch deltas may later be created from them. The absence of this flag shall
137 cause skipped releases to be nonexistent in the SCCS file, preventing branch deltas from being created from them in the future.
138 During the initial creation of an SCCS file, the <b>n</b> flag may be ignored; that is, if the <b>-r</b> option is used to set the
139 release number of the initial SID to a value greater than 1, null deltas need not be created for the "skipped" releases.</dd>
140 <dt><b>q</b><i>text</i></dt>
141 <dd>Substitute user-definable <i>text</i> for all occurrences of the %<b>Q</b>% keyword in the SCCS file text retrieved by <a href=
142 "../utilities/get.html"><i>get</i></a>.</dd>
143 <dt><b>m</b><i>mod</i></dt>
144 <dd>Specify the module name of the SCCS file substituted for all occurrences of the %<b>M</b>% keyword in the SCCS file text
145 retrieved by <a href="../utilities/get.html"><i>get</i></a>. If the <b>m</b> flag is not specified, the value assigned shall be the
146 name of the SCCS file with the leading <tt>'.'</tt> removed.</dd>
147 <dt><b>t</b><i>type</i></dt>
148 <dd>Specify the <i>type</i> of module in the SCCS file substituted for all occurrences of the %<b>Y</b>% keyword in the SCCS file
149 text retrieved by <a href="../utilities/get.html"><i>get</i></a>.</dd>
150 <dt><b>v</b><i>pgm</i></dt>
151 <dd>Cause <a href="../utilities/delta.html"><i>delta</i></a> to prompt for modification request (MR) numbers as the reason for
152 creating a delta. The optional value specifies the name of an MR number validation program. (If this flag is set when creating an
153 SCCS file, the application shall ensure that the <b>m</b> option is also used even if its value is null.)</dd>
154 </dl>
155 </dd>
156 <dt><b>-d </b><i>flag</i></dt>
157 <dd>Remove (delete) the specified <i>flag</i> from an SCCS file. Several <b>-d</b> options may be supplied on a single <i>admin</i>
158 command. See the <b>-f</b> option for allowable <i>flag</i> names. (The <b>l</b><i>list</i> flag gives a <i>list</i> of releases to
159 be unlocked. See the <b>-f</b> option for further description of the <b>l</b> flag and the syntax of a <i>list</i>.)</dd>
160 <dt><b>-a </b><i>login</i></dt>
161 <dd>Specify a <i>login</i> name, or numerical group ID, to be added to the list of users who may make deltas (changes) to the SCCS
162 file. A group ID shall be equivalent to specifying all <i>login</i> names common to that group ID. Several <b>-a</b> options may be
163 used on a single <i>admin</i> command line. As many <i>login</i>s, or numerical group IDs, as desired may be on the list
164 simultaneously. If the list of users is empty, then anyone may add deltas. If <i>login</i> or group ID is preceded by a
165 <tt>'!'</tt>, the users so specified shall be denied permission to make deltas.</dd>
166 <dt><b>-e </b><i>login</i></dt>
167 <dd>Specify a <i>login</i> name, or numerical group ID, to be erased from the list of users allowed to make deltas (changes) to the
168 SCCS file. Specifying a group ID is equivalent to specifying all <i>login</i> names common to that group ID. Several <b>-e</b>
169 options may be used on a single <i>admin</i> command line.</dd>
170 <dt><b>-y[</b><i>comment</i><b>]</b></dt>
171 <dd>Insert the <i>comment</i> text into the SCCS file as a comment for the initial delta in a manner identical to that of <a href=
172 "../utilities/delta.html"><i>delta</i></a>. In the POSIX locale, omission of the <b>-y</b> option shall result in a default comment
173 line being inserted in the form:
174 <pre>
175 <tt>"date and time created %s %s by %s", <</tt><i>date</i><tt>>, <</tt><i>time</i><tt>>, <</tt><i>login</i><tt>>
176 </tt></pre>
177 <p>where <<i>date</i>> is expressed in the format of the <a href="../utilities/date.html"><i>date</i></a> utility's
178 <tt>%y</tt>/<tt>%m</tt>/<tt>%d</tt> conversion specification, <<i>time</i>> in the format of the <a href=
179 "../utilities/date.html"><i>date</i></a> utility's <tt>%T</tt> conversion specification format, and <<i>login</i>> is the
180 login name of the user creating the file.</p>
181 </dd>
182 <dt><b>-m </b><i>mrlist</i></dt>
183 <dd>Insert the list of modification request (MR) numbers into the SCCS file as the reason for creating the initial delta in a
184 manner identical to <a href="../utilities/delta.html"><i>delta</i></a>. The application shall ensure that the <b>v</b> flag is set
185 and the MR numbers are validated if the <b>v</b> flag has a value (the name of an MR number validation program). A diagnostic
186 message shall be written if the <b>v</b> flag is not set or MR validation fails.</dd>
187 <dt><b>-h</b></dt>
188 <dd>Check the structure of the SCCS file and compare the newly computed checksum with the checksum that is stored in the SCCS file.
189 If the newly computed checksum does not match the checksum in the SCCS file, a diagnostic message shall be written.</dd>
190 <dt><b>-z</b></dt>
191 <dd>Recompute the SCCS file checksum and store it in the first line of the SCCS file (see the <b>-h</b> option above). Note that
192 use of this option on a truly corrupted file may prevent future detection of the corruption.</dd>
193 </dl>
194 </blockquote>
195 <h4 class="mansect"><a name="tag_20_01_05" id="tag_20_01_05"></a>OPERANDS</h4>
196 <blockquote>
197 <p>The following operands shall be supported:</p>
198 <dl compact>
199 <dd></dd>
200 <dt><i>file</i></dt>
201 <dd>A pathname of an existing SCCS file or a directory. If <i>file</i> is a directory, the <i>admin</i> utility shall behave as
202 though each file in the directory were specified as a named file, except that non-SCCS files (last component of the pathname does
203 not begin with <b>s.</b>) and unreadable files shall be silently ignored.</dd>
204 <dt><i>newfile</i></dt>
205 <dd>A pathname of an SCCS file to be created.</dd>
206 </dl>
207 <p>If exactly one <i>file</i> or <i>newfile</i> operand appears, and it is <tt>'-'</tt>, the standard input shall be read; each
208 line of the standard input shall be taken to be the name of an SCCS file to be processed. Non-SCCS files and unreadable files shall
209 be silently ignored.</p>
210 </blockquote>
211 <h4 class="mansect"><a name="tag_20_01_06" id="tag_20_01_06"></a>STDIN</h4>
212 <blockquote>
213 <p>The standard input shall be a text file used only if <b>-i</b> is specified without an option-argument or if a <i>file</i> or
214 <i>newfile</i> operand is specified as <tt>'-'</tt>. If the first character of any standard input line is <SOH> in the POSIX
215 locale, the results are unspecified.</p>
216 </blockquote>
217 <h4 class="mansect"><a name="tag_20_01_07" id="tag_20_01_07"></a>INPUT FILES</h4>
218 <blockquote>
219 <p>The existing SCCS files shall be text files of an unspecified format.</p>
220 <p>The application shall ensure that the file named by the <b>-i</b> option's <i>name</i> option-argument shall be a text file; if
221 the first character of any line in this file is <SOH> in the POSIX locale, the results are unspecified. If this file contains
222 more than 99999 lines, the number of lines recorded in the header for this file shall be 99999 for this delta.</p>
223 </blockquote>
224 <h4 class="mansect"><a name="tag_20_01_08" id="tag_20_01_08"></a>ENVIRONMENT VARIABLES</h4>
225 <blockquote>
226 <p>The following environment variables shall affect the execution of <i>admin</i>:</p>
227 <dl compact>
228 <dd></dd>
229 <dt><i>LANG</i></dt>
230 <dd>Provide a default value for the internationalization variables that are unset or null. (See XBD <a href=
231 "../basedefs/V1_chap08.html#tag_08_02"><i>8.2 Internationalization Variables</i></a> for the precedence of internationalization
232 variables used to determine the values of locale categories.)</dd>
233 <dt><i>LC_ALL</i></dt>
234 <dd>If set to a non-empty string value, override the values of all the other internationalization variables.</dd>
235 <dt><i>LC_CTYPE</i></dt>
236 <dd>Determine the locale for the interpretation of sequences of bytes of text data as characters (for example, single-byte as
237 opposed to multi-byte characters in arguments and input files).</dd>
238 <dt><i>LC_MESSAGES</i></dt>
239 <dd><br>
240 Determine the locale that should be used to affect the format and contents of diagnostic messages written to standard error and the
241 contents of the default <b>-y</b> comment.</dd>
242 <dt><i>NLSPATH</i></dt>
243 <dd>Determine the location of messages objects and message catalogs.</dd>
244 </dl>
245 </blockquote>
246 <h4 class="mansect"><a name="tag_20_01_09" id="tag_20_01_09"></a>ASYNCHRONOUS EVENTS</h4>
247 <blockquote>
248 <p>Default.</p>
249 </blockquote>
250 <h4 class="mansect"><a name="tag_20_01_10" id="tag_20_01_10"></a>STDOUT</h4>
251 <blockquote>
252 <p>Not used.</p>
253 </blockquote>
254 <h4 class="mansect"><a name="tag_20_01_11" id="tag_20_01_11"></a>STDERR</h4>
255 <blockquote>
256 <p>The standard error shall be used only for diagnostic messages.</p>
257 </blockquote>
258 <h4 class="mansect"><a name="tag_20_01_12" id="tag_20_01_12"></a>OUTPUT FILES</h4>
259 <blockquote>
260 <p>Any SCCS files created shall be text files of an unspecified format. During processing of a <i>file</i>, a locking
261 <i>z-file</i>, as described in <a href="../utilities/get.html#"><i>get</i></a> , may be created and deleted.</p>
262 </blockquote>
263 <h4 class="mansect"><a name="tag_20_01_13" id="tag_20_01_13"></a>EXTENDED DESCRIPTION</h4>
264 <blockquote>
265 <p>None.</p>
266 </blockquote>
267 <h4 class="mansect"><a name="tag_20_01_14" id="tag_20_01_14"></a>EXIT STATUS</h4>
268 <blockquote>
269 <p>The following exit values shall be returned:</p>
270 <dl compact>
271 <dd></dd>
272 <dt> 0</dt>
273 <dd>Successful completion.</dd>
274 <dt>>0</dt>
275 <dd>An error occurred.</dd>
276 </dl>
277 </blockquote>
278 <h4 class="mansect"><a name="tag_20_01_15" id="tag_20_01_15"></a>CONSEQUENCES OF ERRORS</h4>
279 <blockquote>
280 <p>Default.</p>
281 </blockquote>
282 <hr>
283 <div class="box"><em>The following sections are informative.</em></div>
284 <h4 class="mansect"><a name="tag_20_01_16" id="tag_20_01_16"></a>APPLICATION USAGE</h4>
285 <blockquote>
286 <p>It is recommended that directories containing SCCS files be writable by the owner only, and that SCCS files themselves be
287 read-only. The mode of the directories should allow only the owner to modify SCCS files contained in the directories. The mode of
288 the SCCS files prevents any modification at all except by SCCS commands.</p>
289 </blockquote>
290 <h4 class="mansect"><a name="tag_20_01_17" id="tag_20_01_17"></a>EXAMPLES</h4>
291 <blockquote>
292 <p>None.</p>
293 </blockquote>
294 <h4 class="mansect"><a name="tag_20_01_18" id="tag_20_01_18"></a>RATIONALE</h4>
295 <blockquote>
296 <p>None.</p>
297 </blockquote>
298 <h4 class="mansect"><a name="tag_20_01_19" id="tag_20_01_19"></a>FUTURE DIRECTIONS</h4>
299 <blockquote>
300 <p>If this utility is directed to display a pathname that contains any bytes that have the encoded value of a <newline>
301 character when <newline> is a terminator or separator in the output format being used, implementations are encouraged to
302 treat this as an error. A future version of this standard may require implementations to treat this as an error.</p>
303 <p>If this utility is directed to create a new directory entry that contains any bytes that have the encoded value of a
304 <newline> character, implementations are encouraged to treat this as an error. A future version of this standard may require
305 implementations to treat this as an error.</p>
306 </blockquote>
307 <h4 class="mansect"><a name="tag_20_01_20" id="tag_20_01_20"></a>SEE ALSO</h4>
308 <blockquote>
309 <p><a href="../utilities/delta.html#"><i>delta</i></a> , <a href="../utilities/get.html#"><i>get</i></a> , <a href=
310 "../utilities/prs.html#"><i>prs</i></a> , <a href="../utilities/what.html#"><i>what</i></a></p>
311 <p>XBD <a href="../basedefs/V1_chap08.html#tag_08"><i>8. Environment Variables</i></a> , <a href=
312 "../basedefs/V1_chap12.html#tag_12_02"><i>12.2 Utility Syntax Guidelines</i></a></p>
313 </blockquote>
314 <h4 class="mansect"><a name="tag_20_01_21" id="tag_20_01_21"></a>CHANGE HISTORY</h4>
315 <blockquote>
316 <p>First released in Issue 2.</p>
317 </blockquote>
318 <h4 class="mansect"><a name="tag_20_01_22" id="tag_20_01_22"></a>Issue 6</h4>
319 <blockquote>
320 <p>The normative text is reworded to avoid use of the term "must" for application requirements, and to emphasize the term
321 "shall" for implementation requirements.</p>
322 <p>The grammar is updated.</p>
323 <p>The Open Group Base Resolution bwg2001-007 is applied, adding new text to the INPUT FILES section warning that the maximum lines
324 recorded in the file is 99999.</p>
325 <p>The Open Group Base Resolution bwg2001-009 is applied, amending the description of the <b>-h</b> option.</p>
326 </blockquote>
327 <h4 class="mansect"><a name="tag_20_01_23" id="tag_20_01_23"></a>Issue 8</h4>
328 <blockquote>
329 <p>Austin Group Defect 251 is applied, encouraging implementations to behave as follows:</p>
330 <ol type="a">
331 <li>
332 <p>Report an error if a utility is directed to display a pathname that contains any bytes that have the encoded value of a
333 <newline> character when <newline> is a terminator or separator in the output format being used.</p>
334 </li>
335 <li>
336 <p>Disallow the creation of filenames containing any bytes that have the encoded value of a <newline> character.</p>
337 </li>
338 </ol>
339 <p>Austin Group Defect 1122 is applied, changing the description of <i>NLSPATH .</i></p>
340 </blockquote>
341 <div class="box"><em>End of informative text.</em></div>
342 <hr>
343 <p> </p>
344 <a href="#top"><span class="topOfPage">return to top of page</span></a><br>
345 <hr size="2" noshade>
346 <center><font size="2">UNIX® is a registered Trademark of The Open Group.<br>
347 POSIX™ is a Trademark of The IEEE.<br>
348 Copyright © 2001-2024 The IEEE and The Open Group, All Rights Reserved<br>
349 [ <a href="../mindex.html">Main Index</a> | <a href="../basedefs/contents.html">XBD</a> | <a href=
350 "../functions/contents.html">XSH</a> | <a href="../utilities/contents.html">XCU</a> | <a href="../xrat/contents.html">XRAT</a>
351 ]</font></center>
352 <hr size="2" noshade>
353 <div class="NAVHEADER">
354 <table summary="Header navigation table" class="nav" width="100%" border="0" cellpadding="0" cellspacing="0">
355 <tr class="nav">
356 <td class="nav" width="15%" align="left" valign="bottom"><a href="../utilities/V3_chap03.html" accesskey="P"><<<
357 Previous</a></td>
358 <td class="nav" width="70%" align="center" valign="bottom"><a href="contents.html">Home</a></td>
359 <td class="nav" width="15%" align="right" valign="bottom"><a href="../utilities/alias.html" accesskey="N">Next
360 >>></a></td>
361 </tr>
362 </table>
363 <hr align="left" width="100%"></div>
364 </body>
365 </html>