CP(1)                      POSIX Programmer's Manual                     CP(1)



PPRROOLLOOGG
       This manual page is part of the POSIX Programmer's Manual.  The OS
       implementation of this interface may differ (consult the corresponding
       OS manual page for details of OS behavior), or the interface may not be
       implemented on OS.

NNAAMMEE
       cp -- copy files

SSYYNNOOPPSSIISS
       cp [[-Pfip]] _s_o_u_r_c_e___f_i_l_e _t_a_r_g_e_t___f_i_l_e

       cp [[-Pfip]] _s_o_u_r_c_e___f_i_l_e... _t_a_r_g_e_t

       cp -R [[-H|-L|-P]] [[-fip]] _s_o_u_r_c_e___f_i_l_e... _t_a_r_g_e_t

DDEESSCCRRIIPPTTIIOONN
       The first synopsis form is denoted by two operands, neither of which
       are existing files of type directory. The _c_p utility shall copy the
       contents of _s_o_u_r_c_e___f_i_l_e (or, if _s_o_u_r_c_e___f_i_l_e is a file of type symbolic
       link, the contents of the file referenced by _s_o_u_r_c_e___f_i_l_e) to the
       destination path named by _t_a_r_g_e_t___f_i_l_e_.

       The second synopsis form is denoted by two or more operands where the
       --RR option is not specified and the first synopsis form is not
       applicable. It shall be an error if any _s_o_u_r_c_e___f_i_l_e is a file of type
       directory, if _t_a_r_g_e_t does not exist, or if _t_a_r_g_e_t does not name a
       directory. The _c_p utility shall copy the contents of each _s_o_u_r_c_e___f_i_l_e
       (or, if _s_o_u_r_c_e___f_i_l_e is a file of type symbolic link, the contents of
       the file referenced by _s_o_u_r_c_e___f_i_l_e) to the destination path named by
       the concatenation of _t_a_r_g_e_t, a single <slash> character if _t_a_r_g_e_t did
       not end in a <slash>, and the last component of _s_o_u_r_c_e___f_i_l_e.

       The third synopsis form is denoted by two or more operands where the --RR
       option is specified. The _c_p utility shall copy each file in the file
       hierarchy rooted in each _s_o_u_r_c_e___f_i_l_e to a destination path named as
       follows:

        *  If _t_a_r_g_e_t exists and names an existing directory, the name of the
           corresponding destination path for each file in the file hierarchy
           shall be the concatenation of _t_a_r_g_e_t, a single <slash> character if
           _t_a_r_g_e_t did not end in a <slash>, and the pathname of the file
           relative to the directory containing _s_o_u_r_c_e___f_i_l_e.

        *  If _t_a_r_g_e_t does not exist and two operands are specified, the name
           of the corresponding destination path for _s_o_u_r_c_e___f_i_l_e shall be
           _t_a_r_g_e_t; the name of the corresponding destination path for all
           other files in the file hierarchy shall be the concatenation of
           _t_a_r_g_e_t, a <slash> character, and the pathname of the file relative
           to _s_o_u_r_c_e___f_i_l_e.

       It shall be an error if _t_a_r_g_e_t does not exist and more than two
       operands are specified, or if _t_a_r_g_e_t exists and does not name a
       directory.

       In the following description, the term _d_e_s_t___f_i_l_e refers to the file
       named by the destination path. The term _s_o_u_r_c_e___f_i_l_e refers to the file
       that is being copied, whether specified as an operand or a file in a
       file hierarchy rooted in a _s_o_u_r_c_e___f_i_l_e operand. If _s_o_u_r_c_e___f_i_l_e is a
       file of type symbolic link:

        *  If the --RR option was not specified, _c_p shall take actions based on
           the type and contents of the file referenced by the symbolic link,
           and not by the symbolic link itself, unless the --PP option was
           specified.

        *  If the --RR option was specified:

           --  If none of the options --HH, --LL, nor --PP were specified, it is
               unspecified which of --HH, --LL, or --PP will be used as a default.

           --  If the --HH option was specified, _c_p shall take actions based on
               the type and contents of the file referenced by any symbolic
               link specified as a _s_o_u_r_c_e___f_i_l_e operand.

           --  If the --LL option was specified, _c_p shall take actions based on
               the type and contents of the file referenced by any symbolic
               link specified as a _s_o_u_r_c_e___f_i_l_e operand or any symbolic links
               encountered during traversal of a file hierarchy.

           --  If the --PP option was specified, _c_p shall copy any symbolic link
               specified as a _s_o_u_r_c_e___f_i_l_e operand and any symbolic links
               encountered during traversal of a file hierarchy, and shall not
               follow any symbolic links.

       For each _s_o_u_r_c_e___f_i_l_e, the following steps shall be taken:

        1. If _s_o_u_r_c_e___f_i_l_e references the same file as _d_e_s_t___f_i_l_e, _c_p may write
           a diagnostic message to standard error; it shall do nothing more
           with _s_o_u_r_c_e___f_i_l_e and shall go on to any remaining files.

        2. If _s_o_u_r_c_e___f_i_l_e is of type directory, the following steps shall be
           taken:

            a. If the --RR option was not specified, _c_p shall write a diagnostic
               message to standard error, do nothing more with _s_o_u_r_c_e___f_i_l_e,
               and go on to any remaining files.

            b. If _s_o_u_r_c_e___f_i_l_e was not specified as an operand and _s_o_u_r_c_e___f_i_l_e
               is dot or dot-dot, _c_p shall do nothing more with _s_o_u_r_c_e___f_i_l_e
               and go on to any remaining files.

            c. If _d_e_s_t___f_i_l_e exists and it is a file type not specified by the
               System Interfaces volume of POSIX.1-2017, the behavior is
               implementation-defined.

            d. If _d_e_s_t___f_i_l_e exists and it is not of type directory, _c_p shall
               write a diagnostic message to standard error, do nothing more
               with _s_o_u_r_c_e___f_i_l_e or any files below _s_o_u_r_c_e___f_i_l_e in the file
               hierarchy, and go on to any remaining files.

            e. If the directory _d_e_s_t___f_i_l_e does not exist, it shall be created
               with file permission bits set to the same value as those of
               _s_o_u_r_c_e___f_i_l_e, modified by the file creation mask of the user if
               the --pp option was not specified, and then bitwise-inclusively
               OR'ed with S_IRWXU. If _d_e_s_t___f_i_l_e cannot be created, _c_p shall
               write a diagnostic message to standard error, do nothing more
               with _s_o_u_r_c_e___f_i_l_e, and go on to any remaining files. It is
               unspecified if _c_p attempts to copy files in the file hierarchy
               rooted in _s_o_u_r_c_e___f_i_l_e.

            f. The files in the directory _s_o_u_r_c_e___f_i_l_e shall be copied to the
               directory _d_e_s_t___f_i_l_e, taking the four steps (1 to 4) listed here
               with the files as _s_o_u_r_c_e___f_i_l_es.

            g. If _d_e_s_t___f_i_l_e was created, its file permission bits shall be
               changed (if necessary) to be the same as those of _s_o_u_r_c_e___f_i_l_e,
               modified by the file creation mask of the user if the --pp option
               was not specified.

            h. The _c_p utility shall do nothing more with _s_o_u_r_c_e___f_i_l_e and go on
               to any remaining files.

        3. If _s_o_u_r_c_e___f_i_l_e is of type regular file, the following steps shall
           be taken:

            a. The behavior is unspecified if _d_e_s_t___f_i_l_e exists and was written
               by a previous step. Otherwise, if _d_e_s_t___f_i_l_e exists, the
               following steps shall be taken:

                i.  If the --ii option is in effect, the _c_p utility shall write
                    a prompt to the standard error and read a line from the
                    standard input. If the response is not affirmative, _c_p
                    shall do nothing more with _s_o_u_r_c_e___f_i_l_e and go on to any
                    remaining files.

               ii.  A file descriptor for _d_e_s_t___f_i_l_e shall be obtained by
                    performing actions equivalent to the _o_p_e_n() function
                    defined in the System Interfaces volume of POSIX.1-2017
                    called using _d_e_s_t___f_i_l_e as the _p_a_t_h argument, and the
                    bitwise-inclusive OR of O_WRONLY and O_TRUNC as the _o_f_l_a_g
                    argument.

               iii. If the attempt to obtain a file descriptor fails and the
                    --ff option is in effect, _c_p shall attempt to remove the
                    file by performing actions equivalent to the _u_n_l_i_n_k()
                    function defined in the System Interfaces volume of
                    POSIX.1-2017 called using _d_e_s_t___f_i_l_e as the _p_a_t_h argument.
                    If this attempt succeeds, _c_p shall continue with step 3b.

            b. If _d_e_s_t___f_i_l_e does not exist, a file descriptor shall be
               obtained by performing actions equivalent to the _o_p_e_n()
               function defined in the System Interfaces volume of
               POSIX.1-2017 called using _d_e_s_t___f_i_l_e as the _p_a_t_h argument, and
               the bitwise-inclusive OR of O_WRONLY and O_CREAT as the _o_f_l_a_g
               argument. The file permission bits of _s_o_u_r_c_e___f_i_l_e shall be the
               _m_o_d_e argument.

            c. If the attempt to obtain a file descriptor fails, _c_p shall
               write a diagnostic message to standard error, do nothing more
               with _s_o_u_r_c_e___f_i_l_e, and go on to any remaining files.

            d. The contents of _s_o_u_r_c_e___f_i_l_e shall be written to the file
               descriptor. Any write errors shall cause _c_p to write a
               diagnostic message to standard error and continue to step 3e.

            e. The file descriptor shall be closed.

            f. The _c_p utility shall do nothing more with _s_o_u_r_c_e___f_i_l_e.  If a
               write error occurred in step 3d, it is unspecified if _c_p
               continues with any remaining files. If no write error occurred
               in step 3d, _c_p shall go on to any remaining files.

        4. Otherwise, the --RR option was specified, and the following steps
           shall be taken:

            a. The _d_e_s_t___f_i_l_e shall be created with the same file type as
               _s_o_u_r_c_e___f_i_l_e.

            b. If _s_o_u_r_c_e___f_i_l_e is a file of type FIFO, the file permission bits
               shall be the same as those of _s_o_u_r_c_e___f_i_l_e_, modified by the file
               creation mask of the user if the --pp option was not specified.
               Otherwise, the permissions, owner ID, and group ID of _d_e_s_t___f_i_l_e
               are implementation-defined.

               If this creation fails for any reason, _c_p shall write a
               diagnostic message to standard error, do nothing more with
               _s_o_u_r_c_e___f_i_l_e, and go on to any remaining files.

            c. If _s_o_u_r_c_e___f_i_l_e is a file of type symbolic link, and the options
               require the symbolic link itself to be acted upon, the pathname
               contained in _d_e_s_t___f_i_l_e shall be the same as the pathname
               contained in _s_o_u_r_c_e___f_i_l_e.

               If this fails for any reason, _c_p shall write a diagnostic
               message to standard error, do nothing more with _s_o_u_r_c_e___f_i_l_e,
               and go on to any remaining files.

       If the implementation provides additional or alternate access control
       mechanisms (see the Base Definitions volume of POSIX.1-2017, _S_e_c_t_i_o_n
       _4_._5, _F_i_l_e _A_c_c_e_s_s _P_e_r_m_i_s_s_i_o_n_s), their effect on copies of files is
       implementation-defined.

OOPPTTIIOONNSS
       The _c_p utility shall conform to the Base Definitions volume of
       POSIX.1-2017, _S_e_c_t_i_o_n _1_2_._2, _U_t_i_l_i_t_y _S_y_n_t_a_x _G_u_i_d_e_l_i_n_e_s.

       The following options shall be supported:

       --ff        If a file descriptor for a destination file cannot be
                 obtained, as described in step 3.a.ii., attempt to unlink the
                 destination file and proceed.

       --HH        Take actions based on the type and contents of the file
                 referenced by any symbolic link specified as a _s_o_u_r_c_e___f_i_l_e
                 operand.

       --ii        Write a prompt to standard error before copying to any
                 existing non-directory destination file. If the response from
                 the standard input is affirmative, the copy shall be
                 attempted; otherwise, it shall not.

       --LL        Take actions based on the type and contents of the file
                 referenced by any symbolic link specified as a _s_o_u_r_c_e___f_i_l_e
                 operand or any symbolic links encountered during traversal of
                 a file hierarchy.

       --PP        Take actions on any symbolic link specified as a _s_o_u_r_c_e___f_i_l_e
                 operand or any symbolic link encountered during traversal of
                 a file hierarchy.

       --pp        Duplicate the following characteristics of each source file
                 in the corresponding destination file:

                  1. The time of last data modification and time of last
                     access. If this duplication fails for any reason, _c_p
                     shall write a diagnostic message to standard error.

                  2. The user ID and group ID. If this duplication fails for
                     any reason, it is unspecified whether _c_p writes a
                     diagnostic message to standard error.

                  3. The file permission bits and the S_ISUID and S_ISGID
                     bits. Other, implementation-defined, bits may be
                     duplicated as well. If this duplication fails for any
                     reason, _c_p shall write a diagnostic message to standard
                     error.

                 If the user ID or the group ID cannot be duplicated, the file
                 permission bits S_ISUID and S_ISGID shall be cleared. If
                 these bits are present in the source file but are not
                 duplicated in the destination file, it is unspecified whether
                 _c_p writes a diagnostic message to standard error.

                 The order in which the preceding characteristics are
                 duplicated is unspecified. The _d_e_s_t___f_i_l_e shall not be deleted
                 if these characteristics cannot be preserved.

       --RR        Copy file hierarchies.

       Specifying more than one of the mutually-exclusive options --HH, --LL, and
       --PP shall not be considered an error. The last option specified shall
       determine the behavior of the utility.

OOPPEERRAANNDDSS
       The following operands shall be supported:

       _s_o_u_r_c_e___f_i_l_e
                 A pathname of a file to be copied. If a _s_o_u_r_c_e___f_i_l_e operand
                 is ''--'', it shall refer to a file named --; implementations
                 shall not treat it as meaning standard input.

       _t_a_r_g_e_t___f_i_l_e
                 A pathname of an existing or nonexistent file, used for the
                 output when a single file is copied. If a _t_a_r_g_e_t___f_i_l_e operand
                 is ''--'', it shall refer to a file named --; implementations
                 shall not treat it as meaning standard output.

       _t_a_r_g_e_t    A pathname of a directory to contain the copied files.

SSTTDDIINN
       The standard input shall be used to read an input line in response to
       each prompt specified in the STDERR section. Otherwise, the standard
       input shall not be used.

IINNPPUUTT FFIILLEESS
       The input files specified as operands may be of any file type.

EENNVVIIRROONNMMEENNTT VVAARRIIAABBLLEESS
       The following environment variables shall affect the execution of _c_p:

       _L_A_N_G      Provide a default value for the internationalization
                 variables that are unset or null. (See the Base Definitions
                 volume of POSIX.1-2017, _S_e_c_t_i_o_n _8_._2, _I_n_t_e_r_n_a_t_i_o_n_a_l_i_z_a_t_i_o_n
                 _V_a_r_i_a_b_l_e_s for the precedence of internationalization
                 variables used to determine the values of locale categories.)

       _L_C___A_L_L    If set to a non-empty string value, override the values of
                 all the other internationalization variables.

       _L_C___C_O_L_L_A_T_E
                 Determine the locale for the behavior of ranges, equivalence
                 classes, and multi-character collating elements used in the
                 extended regular expression defined for the yyeesseexxpprr locale
                 keyword in the _L_C___M_E_S_S_A_G_E_S category.

       _L_C___C_T_Y_P_E  Determine the locale for the interpretation of sequences of
                 bytes of text data as characters (for example, single-byte as
                 opposed to multi-byte characters in arguments and input
                 files) and the behavior of character classes used in the
                 extended regular expression defined for the yyeesseexxpprr locale
                 keyword in the _L_C___M_E_S_S_A_G_E_S category.

       _L_C___M_E_S_S_A_G_E_S
                 Determine the locale used to process affirmative responses,
                 and the locale used to affect the format and contents of
                 diagnostic messages and prompts written to standard error.

       _N_L_S_P_A_T_H   Determine the location of message catalogs for the processing
                 of _L_C___M_E_S_S_A_G_E_S.

AASSYYNNCCHHRROONNOOUUSS EEVVEENNTTSS
       Default.

SSTTDDOOUUTT
       Not used.

SSTTDDEERRRR
       A prompt shall be written to standard error under the conditions
       specified in the DESCRIPTION section. The prompt shall contain the
       destination pathname, but its format is otherwise unspecified.
       Otherwise, the standard error shall be used only for diagnostic
       messages.

OOUUTTPPUUTT FFIILLEESS
       The output files may be of any type.

EEXXTTEENNDDEEDD DDEESSCCRRIIPPTTIIOONN
       None.

EEXXIITT SSTTAATTUUSS
       The following exit values shall be returned:

        0    All files were copied successfully.

       >0    An error occurred.

CCOONNSSEEQQUUEENNCCEESS OOFF EERRRROORRSS
       If _c_p is prematurely terminated by a signal or error, files or file
       hierarchies may be only partially copied and files and directories may
       have incorrect permissions or access and modification times.

       _T_h_e _f_o_l_l_o_w_i_n_g _s_e_c_t_i_o_n_s _a_r_e _i_n_f_o_r_m_a_t_i_v_e_.

AAPPPPLLIICCAATTIIOONN UUSSAAGGEE
       The set-user-ID and set-group-ID bits are explicitly cleared when files
       are created. This is to prevent users from creating programs that are
       set-user-ID or set-group-ID to them when copying files or to make set-
       user-ID or set-group-ID files accessible to new groups of users.  For
       example, if a file is set-user-ID and the copy has a different group ID
       than the source, a new group of users has execute permission to a set-
       user-ID program than did previously. In particular, this is a problem
       for superusers copying users' trees.

EEXXAAMMPPLLEESS
       None.

RRAATTIIOONNAALLEE
       The --ii option exists on BSD systems, giving applications and users a
       way to avoid accidentally removing files when copying. Although the 4.3
       BSD version does not prompt if the standard input is not a terminal,
       the standard developers decided that use of --ii is a request for
       interaction, so when the destination path exists, the utility takes
       instructions from whatever responds on standard input.

       The exact format of the interactive prompts is unspecified. Only the
       general nature of the contents of prompts are specified because
       implementations may desire more descriptive prompts than those used on
       historical implementations. Therefore, an application using the --ii
       option relies on the system to provide the most suitable dialog
       directly with the user, based on the behavior specified.

       The --pp option is historical practice on BSD systems, duplicating the
       time of last data modification and time of last access. This volume of
       POSIX.1-2017 extends it to preserve the user and group IDs, as well as
       the file permissions. This requirement has obvious problems in that the
       directories are almost certainly modified after being copied. This
       volume of POSIX.1-2017 requires that the modification times be
       preserved. The statement that the order in which the characteristics
       are duplicated is unspecified is to permit implementations to provide
       the maximum amount of security for the user.  Implementations should
       take into account the obvious security issues involved in setting the
       owner, group, and mode in the wrong order or creating files with an
       owner, group, or mode different from the final value.

       It is unspecified whether _c_p writes diagnostic messages when the user
       and group IDs cannot be set due to the widespread practice of users
       using --pp to duplicate some portion of the file characteristics,
       indifferent to the duplication of others. Historic implementations only
       write diagnostic messages on errors other than [[EEPPEERRMM]].

       Earlier versions of this standard included support for the --rr option to
       copy file hierarchies. The --rr option is historical practice on BSD and
       BSD-derived systems. This option is no longer specified by POSIX.1-2008
       but may be present in some implementations. The --RR option was added as
       a close synonym to the --rr option, selected for consistency with all
       other options in this volume of POSIX.1-2017 that do recursive
       directory descent.

       The difference between --RR and the removed --rr option is in the treatment
       by _c_p of file types other than regular and directory. It was
       implementation-defined how the -- option treated special files to allow
       both historical implementations and those that chose to support --rr with
       the same abilities as --RR defined by this volume of POSIX.1-2017. The
       original --rr flag, for historic reasons, did not handle special files
       any differently from regular files, but always read the file and copied
       its contents. This had obvious problems in the presence of special file
       types; for example, character devices, FIFOs, and sockets.

       When a failure occurs during the copying of a file hierarchy, _c_p is
       required to attempt to copy files that are on the same level in the
       hierarchy or above the file where the failure occurred. It is
       unspecified if _c_p shall attempt to copy files below the file where the
       failure occurred (which cannot succeed in any case).

       Permissions, owners, and groups of created special file types have been
       deliberately left as implementation-defined. This is to allow systems
       to satisfy special requirements (for example, allowing users to create
       character special devices, but requiring them to be owned by a certain
       group). In general, it is strongly suggested that the permissions,
       owner, and group be the same as if the user had run the historical
       _m_k_n_o_d, _l_n, or other utility to create the file. It is also probable
       that additional privileges are required to create block, character, or
       other implementation-defined special file types.

       Additionally, the --pp option explicitly requires that all set-user-ID
       and set-group-ID permissions be discarded if any of the owner or group
       IDs cannot be set. This is to keep users from unintentionally giving
       away special privilege when copying programs.

       When creating regular files, historical versions of _c_p use the mode of
       the source file as modified by the file mode creation mask. Other
       choices would have been to use the mode of the source file unmodified
       by the creation mask or to use the same mode as would be given to a new
       file created by the user (plus the execution bits of the source file)
       and then modify it by the file mode creation mask. In the absence of
       any strong reason to change historic practice, it was in large part
       retained.

       When creating directories, historical versions of _c_p use the mode of
       the source directory, plus read, write, and search bits for the owner,
       as modified by the file mode creation mask. This is done so that _c_p can
       copy trees where the user has read permission, but the owner does not.
       A side-effect is that if the file creation mask denies the owner
       permissions, _c_p fails. Also, once the copy is done, historical versions
       of _c_p set the permissions on the created directory to be the same as
       the source directory, unmodified by the file creation mask.

       This behavior has been modified so that _c_p is always able to create the
       contents of the directory, regardless of the file creation mask. After
       the copy is done, the permissions are set to be the same as the source
       directory, as modified by the file creation mask. This latter change
       from historical behavior is to prevent users from accidentally creating
       directories with permissions beyond those they would normally set and
       for consistency with the behavior of _c_p in creating files.

       It is not a requirement that _c_p detect attempts to copy a file to
       itself; however, implementations are strongly encouraged to do so.
       Historical implementations have detected the attempt in most cases.

       There are two methods of copying subtrees in this volume of
       POSIX.1-2017. The other method is described as part of the _p_a_x utility
       (see _p_a_x).  Both methods are historical practice. The _c_p utility
       provides a simpler, more intuitive interface, while _p_a_x offers a finer
       granularity of control. Each provides additional functionality to the
       other; in particular, _p_a_x maintains the hard-link structure of the
       hierarchy, while _c_p does not. It is the intention of the standard
       developers that the results be similar (using appropriate option
       combinations in both utilities). The results are not required to be
       identical; there seemed insufficient gain to applications to balance
       the difficulty of implementations having to guarantee that the results
       would be exactly identical.

       The wording allowing _c_p to copy a directory to implementation-defined
       file types not specified by the System Interfaces volume of
       POSIX.1-2017 is provided so that implementations supporting symbolic
       links are not required to prohibit copying directories to symbolic
       links. Other extensions to the System Interfaces volume of POSIX.1-2017
       file types may need to use this loophole as well.

FFUUTTUURREE DDIIRREECCTTIIOONNSS
       None.

SSEEEE AALLSSOO
       _m_v, _f_i_n_d, _l_n, _p_a_x

       The Base Definitions volume of POSIX.1-2017, _S_e_c_t_i_o_n _4_._5, _F_i_l_e _A_c_c_e_s_s
       _P_e_r_m_i_s_s_i_o_n_s, _C_h_a_p_t_e_r _8, _E_n_v_i_r_o_n_m_e_n_t _V_a_r_i_a_b_l_e_s, _S_e_c_t_i_o_n _1_2_._2, _U_t_i_l_i_t_y
       _S_y_n_t_a_x _G_u_i_d_e_l_i_n_e_s

       The System Interfaces volume of POSIX.1-2017, _o_p_e_n(), _u_n_l_i_n_k()

CCOOPPYYRRIIGGHHTT
       Portions of this text are reprinted and reproduced in electronic form
       from IEEE Std 1003.1-2017, Standard for Information Technology --
       Portable Operating System Interface (POSIX), The Open Group Base
       Specifications Issue 7, 2018 Edition, Copyright (C) 2018 by the
       Institute of Electrical and Electronics Engineers, Inc and The Open
       Group.  In the event of any discrepancy between this version and the
       original IEEE and The Open Group Standard, the original IEEE and The
       Open Group Standard is the referee document. The original Standard can
       be obtained online at http://www.opengroup.org/unix/online.html .

       Any typographical or formatting errors that appear in this page are
       most likely to have been introduced during the conversion of the source
       files to man page format. To report such errors, see
       https://www.kernel.org/doc/man-pages/reporting_bugs.html .



IEEE/The Open Group                  2017                                CP(1)
