logo

oasis-root

Compiled tree of Oasis Linux based on own branch at <https://hacktivis.me/git/oasis/> git clone https://anongit.hacktivis.me/git/oasis-root.git

set.1p (19879B)


  1. '\" et
  2. .TH SET "1P" 2017 "IEEE/The Open Group" "POSIX Programmer's Manual"
  3. .\"
  4. .SH PROLOG
  5. This manual page is part of the POSIX Programmer's Manual.
  6. The Linux implementation of this interface may differ (consult
  7. the corresponding Linux manual page for details of Linux behavior),
  8. or the interface may not be implemented on Linux.
  9. .\"
  10. .SH NAME
  11. set
  12. \(em set or unset options and positional parameters
  13. .SH SYNOPSIS
  14. .LP
  15. .nf
  16. set \fB[\fR-abCefhmnuvx\fB] [\fR-o \fIoption\fB] [\fIargument\fR...\fB]\fR
  17. .P
  18. set \fB[\fR+abCefhmnuvx\fB] [\fR+o \fIoption\fB] [\fIargument\fR...\fB]\fR
  19. .P
  20. set --\fB [\fIargument\fR...\fB]\fR
  21. .P
  22. set -o
  23. .P
  24. set +o
  25. .fi
  26. .SH DESCRIPTION
  27. If no
  28. .IR option s
  29. or
  30. .IR argument s
  31. are specified,
  32. .IR set
  33. shall write the names and values of all shell variables in the collation
  34. sequence of the current locale. Each
  35. .IR name
  36. shall start on a separate line, using the format:
  37. .sp
  38. .RS 4
  39. .nf
  40. "%s=%s\en", <\fIname\fR>, <\fIvalue\fR>
  41. .fi
  42. .P
  43. .RE
  44. .P
  45. The
  46. .IR value
  47. string shall be written with appropriate quoting; see the description
  48. of shell quoting in
  49. .IR "Section 2.2" ", " "Quoting".
  50. The output shall be suitable for reinput to the shell, setting or
  51. resetting, as far as possible, the variables that are currently set;
  52. read-only variables cannot be reset.
  53. .P
  54. When options are specified, they shall set or unset attributes of the
  55. shell, as described below. When
  56. .IR argument s
  57. are specified, they cause positional parameters to be set or unset, as
  58. described below. Setting or unsetting attributes and positional
  59. parameters are not necessarily related actions, but they can be
  60. combined in a single invocation of
  61. .IR set .
  62. .P
  63. The
  64. .IR set
  65. special built-in shall support the Base Definitions volume of POSIX.1\(hy2017,
  66. .IR "Section 12.2" ", " "Utility Syntax Guidelines"
  67. except that options can be specified with either a leading
  68. <hyphen-minus>
  69. (meaning enable the option) or
  70. <plus-sign>
  71. (meaning disable it) unless otherwise specified.
  72. .P
  73. Implementations shall support the options in the following list in both
  74. their
  75. <hyphen-minus>
  76. and
  77. <plus-sign>
  78. forms. These options can also be specified as options to
  79. .IR sh .
  80. .IP "\fB\-a\fP" 6
  81. When this option is on, the
  82. .IR export
  83. attribute shall be set for each variable to which an assignment is
  84. performed; see the Base Definitions volume of POSIX.1\(hy2017,
  85. .IR "Section 4.23" ", " "Variable Assignment".
  86. If the assignment precedes a utility name in a command, the
  87. .IR export
  88. attribute shall not persist in the current execution environment after
  89. the utility completes, with the exception that preceding one of the
  90. special built-in utilities causes the
  91. .IR export
  92. attribute to persist after the built-in has completed. If the
  93. assignment does not precede a utility name in the command, or if the
  94. assignment is a result of the operation of the
  95. .IR getopts
  96. or
  97. .IR read
  98. utilities, the
  99. .IR export
  100. attribute shall persist until the variable is unset.
  101. .IP "\fB\-b\fP" 6
  102. This option shall be supported if the implementation supports the User
  103. Portability Utilities option. It shall cause the shell to notify the
  104. user asynchronously of background job completions. The following
  105. message is written to standard error:
  106. .RS 6
  107. .sp
  108. .RS 4
  109. .nf
  110. "[%d]%c %s%s\en", <\fIjob-number\fR>, <\fIcurrent\fR>, <\fRstatus\fR>, <\fRjob-name\fR>
  111. .fi
  112. .P
  113. .RE
  114. .P
  115. where the fields shall be as follows:
  116. .IP "<\fIcurrent\fR>" 12
  117. The character
  118. .BR '+'
  119. identifies the job that would be used as a default for the
  120. .IR fg
  121. or
  122. .IR bg
  123. utilities; this job can also be specified using the
  124. .IR job_id
  125. .BR \(dq%+\(dq
  126. or
  127. .BR \(dq%%\(dq .
  128. The character
  129. .BR '\-'
  130. identifies the job that would become the
  131. default if the current default job were to exit; this job can also be
  132. specified using the
  133. .IR job_id
  134. .BR \(dq%-\(dq .
  135. For other jobs, this field is a
  136. <space>.
  137. At most one job can be identified with
  138. .BR '+'
  139. and at most one job can be identified with
  140. .BR '\-' .
  141. If there is any suspended job, then the current job shall be a
  142. suspended job. If there are at least two suspended jobs, then the
  143. previous job also shall be a suspended job.
  144. .IP "<\fIjob-number\fR>" 12
  145. A number that can be used to identify the process group to the
  146. .IR wait ,
  147. .IR fg ,
  148. .IR bg ,
  149. and
  150. .IR kill
  151. utilities. Using these utilities, the job can be identified by
  152. prefixing the job number with
  153. .BR '%' .
  154. .IP "<\fIstatus\fR>" 12
  155. Unspecified.
  156. .IP "<\fIjob-name\fR>" 12
  157. Unspecified.
  158. .P
  159. When the shell notifies the user a job has been completed, it may
  160. remove the job's process ID from the list of those known in the current
  161. shell execution environment; see
  162. .IR "Section 2.9.3.1" ", " "Examples".
  163. Asynchronous notification shall not be enabled by default.
  164. .RE
  165. .IP "\fB\-C\fP" 6
  166. (Uppercase C.) Prevent existing files from being overwritten by the
  167. shell's
  168. .BR '>'
  169. redirection operator (see
  170. .IR "Section 2.7.2" ", " "Redirecting Output");
  171. the
  172. .BR \(dq>|\(dq
  173. redirection operator shall override this
  174. .IR noclobber
  175. option for an individual file.
  176. .IP "\fB\-e\fP" 6
  177. When this option is on, when any command fails (for any of the reasons
  178. listed in
  179. .IR "Section 2.8.1" ", " "Consequences of Shell Errors"
  180. or by returning an exit status greater than zero), the shell immediately
  181. shall exit, as if by executing the
  182. .IR exit
  183. special built-in utility with no arguments, with the following exceptions:
  184. .RS 6
  185. .IP " 1." 4
  186. The failure of any individual command in a multi-command pipeline shall
  187. not cause the shell to exit. Only the failure of the pipeline itself
  188. shall be considered.
  189. .IP " 2." 4
  190. The
  191. .BR \-e
  192. setting shall be ignored when executing the compound list following the
  193. .BR while ,
  194. .BR until ,
  195. .BR if ,
  196. or
  197. .BR elif
  198. reserved word, a pipeline beginning with the
  199. .BR !
  200. reserved word, or any command of an AND-OR list other than the last.
  201. .IP " 3." 4
  202. If the exit status of a compound command other than a subshell command
  203. was the result of a failure while
  204. .BR \-e
  205. was being ignored, then
  206. .BR \-e
  207. shall not apply to this command.
  208. .P
  209. This requirement applies to the shell environment and each subshell
  210. environment separately. For example, in:
  211. .sp
  212. .RS 4
  213. .nf
  214. set -e; (false; echo one) | cat; echo two
  215. .fi
  216. .P
  217. .RE
  218. .P
  219. the
  220. .IR false
  221. command causes the subshell to exit without executing
  222. .IR "echo one" ;
  223. however,
  224. .IR "echo two"
  225. is executed because the exit status of the pipeline
  226. .IR "(false; echo one) | cat"
  227. is zero.
  228. .RE
  229. .IP "\fB\-f\fP" 6
  230. The shell shall disable pathname expansion.
  231. .IP "\fB\-h\fP" 6
  232. Locate and remember utilities invoked by functions as those functions
  233. are defined (the utilities are normally located when the function is
  234. executed).
  235. .IP "\fB\-m\fP" 6
  236. This option shall be supported if the implementation supports the User
  237. Portability Utilities option. All jobs shall be run in their own
  238. process groups. Immediately before the shell issues a prompt after
  239. completion of the background job, a message reporting the exit status
  240. of the background job shall be written to standard error. If a
  241. foreground job stops, the shell shall write a message to standard error
  242. to that effect, formatted as described by the
  243. .IR jobs
  244. utility. In addition, if a job changes status other than exiting (for
  245. example, if it stops for input or output or is stopped by a SIGSTOP
  246. signal), the shell shall write a similar message immediately prior to
  247. writing the next prompt. This option is enabled by default for
  248. interactive shells.
  249. .IP "\fB\-n\fP" 6
  250. The shell shall read commands but does not execute them; this can be
  251. used to check for shell script syntax errors. An interactive shell may
  252. ignore this option.
  253. .IP "\fB\-o\fP" 6
  254. Write the current settings of the options to standard output in an
  255. unspecified format.
  256. .IP "\fB+o\fP" 6
  257. Write the current option settings to standard output in a format that
  258. is suitable for reinput to the shell as commands that achieve the same
  259. options settings.
  260. .IP "\fB\-o\ \fIoption\fR" 6
  261. .br
  262. This option is supported if the system supports the User Portability
  263. Utilities option. It shall set various options, many of which shall be
  264. equivalent to the single option letters. The following values of
  265. .IR option
  266. shall be supported:
  267. .RS 6
  268. .IP "\fIallexport\fR" 10
  269. Equivalent to
  270. .BR \-a .
  271. .IP "\fIerrexit\fR" 10
  272. Equivalent to
  273. .BR \-e .
  274. .IP "\fIignoreeof\fR" 10
  275. Prevent an interactive shell from exiting on end-of-file. This setting
  276. prevents accidental logouts when
  277. <control>\(hyD
  278. is entered. A user shall explicitly
  279. .IR exit
  280. to leave the interactive shell.
  281. .IP "\fImonitor\fR" 10
  282. Equivalent to
  283. .BR \-m .
  284. This option is supported if the system supports the User Portability
  285. Utilities option.
  286. .IP "\fInoclobber\fR" 10
  287. Equivalent to
  288. .BR \-C
  289. (uppercase C).
  290. .IP "\fInoglob\fR" 10
  291. Equivalent to
  292. .BR \-f .
  293. .IP "\fInoexec\fR" 10
  294. Equivalent to
  295. .BR \-n .
  296. .IP "\fInolog\fR" 10
  297. Prevent the entry of function definitions into the command history; see
  298. .IR "Command History List".
  299. .IP "\fInotify\fR" 10
  300. Equivalent to
  301. .BR \-b .
  302. .IP "\fInounset\fR" 10
  303. Equivalent to
  304. .BR \-u .
  305. .IP "\fIverbose\fR" 10
  306. Equivalent to
  307. .BR \-v .
  308. .IP "\fIvi\fR" 10
  309. Allow shell command line editing using the built-in
  310. .IR vi
  311. editor. Enabling
  312. .IR vi
  313. mode shall disable any other command line editing mode provided as an
  314. implementation extension.
  315. .RS 10
  316. .P
  317. It need not be possible to set
  318. .IR vi
  319. mode on for certain block-mode terminals.
  320. .RE
  321. .IP "\fIxtrace\fR" 10
  322. Equivalent to
  323. .BR \-x .
  324. .RE
  325. .IP "\fB\-u\fP" 6
  326. When the shell tries to expand an unset parameter other than the
  327. .BR '@'
  328. and
  329. .BR '*'
  330. special parameters, it shall write a message to standard error and
  331. the expansion shall fail with the consequences specified in
  332. .IR "Section 2.8.1" ", " "Consequences of Shell Errors".
  333. .IP "\fB\-v\fP" 6
  334. The shell shall write its input to standard error as it is read.
  335. .IP "\fB\-x\fP" 6
  336. The shell shall write to standard error a trace for each command after
  337. it expands the command and before it executes it. It is unspecified
  338. whether the command that turns tracing off is traced.
  339. .P
  340. The default for all these options shall be off (unset) unless stated
  341. otherwise in the description of the option or unless the shell was
  342. invoked with them on; see
  343. .IR sh .
  344. .P
  345. The remaining arguments shall be assigned in order to the positional
  346. parameters. The special parameter
  347. .BR '#'
  348. shall be set to reflect the number of positional parameters. All
  349. positional parameters shall be unset before any new values are
  350. assigned.
  351. .P
  352. If the first argument is
  353. .BR '\-' ,
  354. the results are unspecified.
  355. .P
  356. The special argument
  357. .BR \(dq--\(dq
  358. immediately following the
  359. .IR set
  360. command name can be used to delimit the arguments if the first argument
  361. begins with
  362. .BR '+'
  363. or
  364. .BR '\-' ,
  365. or to prevent inadvertent listing of all shell variables when there are
  366. no arguments. The command
  367. .IR set
  368. .BR \-\|\-
  369. without
  370. .IR argument
  371. shall unset all positional parameters and set the special parameter
  372. .BR '#'
  373. to zero.
  374. .SH OPTIONS
  375. See the DESCRIPTION.
  376. .SH OPERANDS
  377. See the DESCRIPTION.
  378. .SH STDIN
  379. Not used.
  380. .SH "INPUT FILES"
  381. None.
  382. .SH "ENVIRONMENT VARIABLES"
  383. None.
  384. .SH "ASYNCHRONOUS EVENTS"
  385. Default.
  386. .SH STDOUT
  387. See the DESCRIPTION.
  388. .SH STDERR
  389. The standard error shall be used only for diagnostic messages.
  390. .SH "OUTPUT FILES"
  391. None.
  392. .SH "EXTENDED DESCRIPTION"
  393. None.
  394. .SH "EXIT STATUS"
  395. .IP "\00" 6
  396. Successful completion.
  397. .IP >0 6
  398. An invalid option was specified, or an error occurred.
  399. .SH "CONSEQUENCES OF ERRORS"
  400. Default.
  401. .LP
  402. .IR "The following sections are informative."
  403. .SH "APPLICATION USAGE"
  404. Application writers should avoid relying on
  405. .IR set
  406. .BR \-e
  407. within functions. For example, in the following script:
  408. .sp
  409. .RS 4
  410. .nf
  411. set -e
  412. start() {
  413. some_server
  414. echo some_server started successfully
  415. }
  416. start || echo >&2 some_server failed
  417. .fi
  418. .P
  419. .RE
  420. .P
  421. the
  422. .BR \-e
  423. setting is ignored within the function body (because the function is a
  424. command in an AND-OR list other than the last). Therefore, if
  425. .IR some_server
  426. fails, the function carries on to echo
  427. .BR \(dqsome_server started successfully\(dq ,
  428. and the exit status of the function is zero (which means
  429. .BR \(dqsome_server failed\(dq
  430. is not output).
  431. .SH EXAMPLES
  432. Write out all variables and their values:
  433. .sp
  434. .RS 4
  435. .nf
  436. set
  437. .fi
  438. .P
  439. .RE
  440. .P
  441. Set $1, $2, and $3 and set
  442. .BR \(dq$#\(dq
  443. to 3:
  444. .sp
  445. .RS 4
  446. .nf
  447. set c a b
  448. .fi
  449. .P
  450. .RE
  451. .P
  452. Turn on the
  453. .BR \-x
  454. and
  455. .BR \-v
  456. options:
  457. .sp
  458. .RS 4
  459. .nf
  460. set -xv
  461. .fi
  462. .P
  463. .RE
  464. .P
  465. Unset all positional parameters:
  466. .sp
  467. .RS 4
  468. .nf
  469. set --
  470. .fi
  471. .P
  472. .RE
  473. .P
  474. Set $1 to the value of
  475. .IR x ,
  476. even if it begins with
  477. .BR '\-'
  478. or
  479. .BR '+' :
  480. .sp
  481. .RS 4
  482. .nf
  483. set -- "$x"
  484. .fi
  485. .P
  486. .RE
  487. .P
  488. Set the positional parameters to the expansion of
  489. .IR x ,
  490. even if
  491. .IR x
  492. expands with a leading
  493. .BR '\-'
  494. or
  495. .BR '+' :
  496. .sp
  497. .RS 4
  498. .nf
  499. set -- $x
  500. .fi
  501. .P
  502. .RE
  503. .SH "RATIONALE"
  504. The
  505. .IR set
  506. \-\|\- form is listed specifically in the SYNOPSIS even though this
  507. usage is implied by the Utility Syntax Guidelines. The explanation of
  508. this feature removes any ambiguity about whether the
  509. .IR set
  510. \-\|\- form might be misinterpreted as being equivalent to
  511. .IR set
  512. without any options or arguments. The functionality of this form has
  513. been adopted from the KornShell. In System V,
  514. .IR set
  515. \-\|\- only unsets parameters if there is at least one argument;
  516. the only way to unset all parameters is to use
  517. .IR shift .
  518. Using the KornShell version should not affect System V scripts because
  519. there should be no reason to issue it without arguments deliberately;
  520. if it were issued as, for example:
  521. .sp
  522. .RS 4
  523. .nf
  524. set -- "$@"
  525. .fi
  526. .P
  527. .RE
  528. .P
  529. and there were in fact no arguments resulting from
  530. .BR \(dq$@\(dq ,
  531. unsetting the parameters would have no result.
  532. .P
  533. The
  534. .IR set
  535. + form in early proposals was omitted as being an unnecessary
  536. duplication of
  537. .IR set
  538. alone and not widespread historical practice.
  539. .P
  540. The
  541. .IR noclobber
  542. option was changed to allow
  543. .IR set
  544. .BR \-C
  545. as well as the
  546. .IR set
  547. .BR \-o
  548. .IR noclobber
  549. option. The single-letter version was added so that the historical
  550. .BR \(dq$-\(dq
  551. paradigm would not be broken; see
  552. .IR "Section 2.5.2" ", " "Special Parameters".
  553. .P
  554. The description of the
  555. .BR \-e
  556. option is intended to match the behavior of the 1988 version of the
  557. KornShell.
  558. .P
  559. The
  560. .BR \-h
  561. flag is related to command name hashing. See
  562. .IR "\fIhash\fR\^".
  563. .P
  564. The following
  565. .IR set
  566. flags were omitted intentionally with the following rationale:
  567. .IP "\fB\-k\fP" 6
  568. The
  569. .BR \-k
  570. flag was originally added by the author of the Bourne shell to make it
  571. easier for users of pre-release versions of the shell. In early
  572. versions of the Bourne shell the construct
  573. .IR set
  574. .IR name =\c
  575. .IR value
  576. had to be used to assign values to shell variables. The problem with
  577. .BR \-k
  578. is that the behavior affects parsing, virtually precluding writing any
  579. compilers. To explain the behavior of
  580. .BR \-k ,
  581. it is necessary to describe the parsing algorithm, which is
  582. implementation-defined. For example:
  583. .RS 6
  584. .sp
  585. .RS 4
  586. .nf
  587. set -k; echo \fIname\fR=\fIvalue\fR
  588. .fi
  589. .P
  590. .RE
  591. .P
  592. and:
  593. .sp
  594. .RS 4
  595. .nf
  596. set -k
  597. echo \fIname\fP=\fIvalue\fR
  598. .fi
  599. .P
  600. .RE
  601. .P
  602. behave differently. The interaction with functions is even more
  603. complex. What is more, the
  604. .BR \-k
  605. flag is never needed, since the command line could have been
  606. reordered.
  607. .RE
  608. .IP "\fB\-t\fP" 6
  609. The
  610. .BR \-t
  611. flag is hard to specify and almost never used. The only known use could
  612. be done with here-documents. Moreover, the behavior with
  613. .IR ksh
  614. and
  615. .IR sh
  616. differs. The reference page says that it exits after reading and
  617. executing one command. What is one command? If the input is
  618. .IR date ;\c
  619. .IR date ,
  620. .IR sh
  621. executes both
  622. .IR date
  623. commands while
  624. .IR ksh
  625. does only the first.
  626. .P
  627. Consideration was given to rewriting
  628. .IR set
  629. to simplify its confusing syntax. A specific suggestion was that the
  630. .IR unset
  631. utility should be used to unset options instead of using the non-\c
  632. \fIgetopt\fR()\c
  633. -able +\c
  634. .IR option
  635. syntax. However, the conclusion was reached that the historical
  636. practice of using +\c
  637. .IR option
  638. was satisfactory and that there was no compelling reason to modify such
  639. widespread historical practice.
  640. .P
  641. The
  642. .BR \-o
  643. option was adopted from the KornShell to address user needs. In
  644. addition to its generally friendly interface,
  645. .BR \-o
  646. is needed to provide the
  647. .IR vi
  648. command line editing mode, for which historical practice yields no
  649. single-letter option name. (Although it might have been possible to
  650. invent such a letter, it was recognized that other editing modes would
  651. be developed and
  652. .BR \-o
  653. provides ample name space for describing such extensions.)
  654. .P
  655. Historical implementations are inconsistent in the format used for
  656. .BR \-o
  657. option status reporting. The
  658. .BR +o
  659. format without an option-argument was added to allow portable access to
  660. the options that can be saved and then later restored using, for
  661. instance, a dot script.
  662. .P
  663. Historically,
  664. .IR sh
  665. did trace the command
  666. .IR set
  667. .BR +x ,
  668. but
  669. .IR ksh
  670. did not.
  671. .P
  672. The
  673. .IR ignoreeof
  674. setting prevents accidental logouts when the end-of-file character
  675. (typically
  676. <control>\(hyD)
  677. is entered. A user shall explicitly
  678. .IR exit
  679. to leave the interactive shell.
  680. .P
  681. The
  682. .IR set
  683. .BR \-m
  684. option was added to apply only to the UPE because it applies primarily
  685. to interactive use, not shell script applications.
  686. .P
  687. The ability to do asynchronous notification became available in the
  688. 1988 version of the KornShell. To have it occur, the user had to issue
  689. the command:
  690. .sp
  691. .RS 4
  692. .nf
  693. trap "jobs -n" CLD
  694. .fi
  695. .P
  696. .RE
  697. .P
  698. The C shell provides two different levels of an asynchronous
  699. notification capability. The environment variable
  700. .IR notify
  701. is analogous to what is done in
  702. .IR set
  703. .BR \-b
  704. or
  705. .IR set
  706. .BR \-o
  707. .IR notify .
  708. When set, it notifies the user immediately of background job
  709. completions. When unset, this capability is turned off.
  710. .P
  711. The other notification ability comes through the built-in utility
  712. .IR notify .
  713. The syntax is:
  714. .sp
  715. .RS 4
  716. .nf
  717. notify \fB[\fR%job ... \fB]\fR
  718. .fi
  719. .P
  720. .RE
  721. .P
  722. By issuing
  723. .IR notify
  724. with no operands, it causes the C shell to notify the user
  725. asynchronously when the state of the current job changes. If given
  726. operands,
  727. .IR notify
  728. asynchronously informs the user of changes in the states of the
  729. specified jobs.
  730. .P
  731. To add asynchronous notification to the POSIX shell, neither the
  732. KornShell extensions to
  733. .IR trap ,
  734. nor the C shell
  735. .IR notify
  736. environment variable seemed appropriate (\c
  737. .IR notify
  738. is not a proper POSIX environment variable name).
  739. .P
  740. The
  741. .IR set
  742. .BR \-b
  743. option was selected as a compromise.
  744. .P
  745. The
  746. .IR notify
  747. built-in was considered to have more functionality than was required
  748. for simple asynchronous notification.
  749. .P
  750. Historically, some shells applied the
  751. .BR \-u
  752. option to all parameters including
  753. .IR $@
  754. and
  755. .IR $* .
  756. The standard developers felt that this was a misfeature since it is
  757. normal and common for
  758. .IR $@
  759. and
  760. .IR $*
  761. to be used in shell scripts regardless of whether they were passed any
  762. arguments. Treating these uses as an error when no arguments are passed
  763. reduces the value of
  764. .BR \-u
  765. for its intended purpose of finding spelling mistakes in variable names
  766. and uses of unset positional parameters.
  767. .SH "FUTURE DIRECTIONS"
  768. None.
  769. .SH "SEE ALSO"
  770. .IR "Section 2.14" ", " "Special Built-In Utilities",
  771. .IR "\fIhash\fR\^"
  772. .P
  773. The Base Definitions volume of POSIX.1\(hy2017,
  774. .IR "Section 4.23" ", " "Variable Assignment",
  775. .IR "Section 12.2" ", " "Utility Syntax Guidelines"
  776. .\"
  777. .SH COPYRIGHT
  778. Portions of this text are reprinted and reproduced in electronic form
  779. from IEEE Std 1003.1-2017, Standard for Information Technology
  780. -- Portable Operating System Interface (POSIX), The Open Group Base
  781. Specifications Issue 7, 2018 Edition,
  782. Copyright (C) 2018 by the Institute of
  783. Electrical and Electronics Engineers, Inc and The Open Group.
  784. In the event of any discrepancy between this version and the original IEEE and
  785. The Open Group Standard, the original IEEE and The Open Group Standard
  786. is the referee document. The original Standard can be obtained online at
  787. http://www.opengroup.org/unix/online.html .
  788. .PP
  789. Any typographical or formatting errors that appear
  790. in this page are most likely
  791. to have been introduced during the conversion of the source files to
  792. man page format. To report such errors, see
  793. https://www.kernel.org/doc/man-pages/reporting_bugs.html .