inetconv(8) 맨 페이지 - 윈디하나의 솔라나라

개요

섹션
맨 페이지 이름
검색(S)

inetconv(8)

inetconv(8)             System Administration Commands             inetconv(8)

NAME
       inetconv  -  convert inetd.conf entries into smf service manifests, im‐
       port them into smf repository

SYNOPSIS
       inetconv -?


       inetconv [-f] [-n] [-i srcfile] [-o destdir]


       inetconv -e [-n] [-i srcfile]

DESCRIPTION
       The  inetconv  utility  converts  a  file  containing  records  of  in‐
       etd.conf(5)  into smf(7) service manifests, and then import those mani‐
       fests into the smf repository. Once the inetd.conf file has  been  con‐
       verted, the only way to change aspects of an inet service is to use the
       inetadm(8) utility.


       There  is a one-to-one correspondence between a service line in the in‐
       put file and the manifest generated.  By  default,  the  manifests  are
       named using the following template:

         <svcname>-<proto>.xml



       The  <svcname>  token is replaced by the service's name and the <proto>
       token by the service's protocol. Any slash (/) characters that exist in
       the source line for the service name or protocol are replaced with  un‐
       derscores (_).


       The service line is recorded as a property of the converted service.


       During  the  conversion  process, if a service line is found to be mal‐
       formed or to be for an internal inetd service, no manifest is generated
       and that service line is skipped.


       The input file is left untouched by the conversion process.

OPTIONS
       The following options are supported:

       -?            Display a usage message.


       -e            Enable smf services which are listed in the input file.


       -f            If a service manifest of the same name as the one  to  be
                     generated is found in the destination directory, inetconv
                     will overwrite that manifest if this option is specified.
                     Otherwise,  an error message is generated and the conver‐
                     sion of that service is not performed.


       -i srcfile    Permits the specification of an alternate input file src‐
                     file. If this option  is  not  specified,  then  the  in‐
                     etd.conf(5) file is used as input.


       -n            Turns off the auto-import of the manifests generated dur‐
                     ing  the conversion process. Later, if you want to import
                     a generated manifest into the smf(7) repository, you  can
                     do so through the use of the svccfg(8) utility.

                     If  the  -e  option is specified, the -n option only dis‐
                     plays the smf services that would be enabled.


       -o destdir    Permits the specification of an alternate destination di‐
                     rectory destdir for the generated manifests. If this  op‐
                     tion  is  not specified, then the manifests are placed in
                     /lib/svc/manifest/network/rpc, if the service  is  a  RPC
                     service, or /lib/svc/manifest/network otherwise.


EXAMPLES
       Example 1 Generating smf Manifests from inetd.conf



       The following command generates smf(7) manifests from newly added lines
       in inetd.conf(5), places them under /lib/svc/manifest, and then imports
       them  into  the  smf repository. Use this command if a network applica‐
       tion's installation stores the inetd configuration  in  inetd.conf  in‐
       stead of smf.


         # inetconv
         100232/10 ->  /lib/svc/manifest/network/100232_10-rpc_udp.xml
         Importing 100232_10-rpc_udp.xml ...Done
         telnet -> /lib/svc/manifest/telnet-tcp6.xml
         Importing telnet-tcp6.xml ...Done


       Example 2 Generating Manifests for Installation Packages



       The  following  command retrieves inetd service properties from a work‐
       space build directory and places the resulting manifests into the  same
       directory. It does not load the manifests into smf. This command may be
       useful  when  porting and packaging a network application for later in‐
       stallation on Solaris.


         # BUILDDIR=/export/build/networkapp
         # inetconv -n -i $BUILDDIR/inet.svcs -o $BUILDDIR
         networkapp -> /export/build/networkapp/networkapp-tcp.xml


EXIT STATUS
       The following exit values are returned:

       0    Operation completed successfully (no errors).


       1    Invalid options specified.


       2    One or more service lines are malformed, and thus  no  manifest(s)
            were generated for them.


       3    An  error  occurred  importing  one or more of the generated mani‐
            fests.


       4    A system error occurred.


FILES
       /lib/svc/manifest/network/{rpc}/<svcname>-<proto>.xml

           Default output manifest file name.


ATTRIBUTES
       See attributes(7) for descriptions of the following attributes:

       tab() box; cw(2.75i) |cw(2.75i) lw(2.75i) |lw(2.75i) ATTRIBUTE  TYPEAT‐
       TRIBUTE VALUE _ Availabilitysystem/network _ Interface StabilityCommit‐
       ted


SEE ALSO
       inetd.conf(5), attributes(7), smf(7), inetadm(8), inetd(8), svccfg(8)

Oracle Solaris 11.4               17 Mar 2021                      inetconv(8)
맨 페이지 내용의 저작권은 맨 페이지 작성자에게 있습니다.
RSS ATOM XHTML 5 CSS3