Tribblix: manual page: inetconv.8

INETCONV(8) Maintenance Commands and Procedures INETCONV(8)

NAME

inetconv - convert inetd.conf entries into smf service manifests,
import 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
inetd.conf(5) into smf(7) service manifests, and then import those
manifests into the smf repository. Once the inetd.conf file has been
converted, 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
input 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
underscores (_).

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

During the conversion process, if a service line is found to be
malformed 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 conversion of that service is not performed.

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

-n
Turns off the auto-import of the manifests generated
during 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
displays the smf services that would be enabled.

-o
Permits the specification of an alternate destination
directory destdir for the generated manifests. If this
option is not specified, then the manifests are placed
in /var/svc/manifest/network/rpc, if the service is a
RPC service, or /var/svc/manifest/network otherwise.

EXAMPLES

Example 1: Generating smf Manifests from inetd.conf

The following command generates smf(7) manifests from inetd.conf(5)
and places them in /var/tmp, overwriting any preexisting manifests of
the same name, and then imports them into the smf repository.

# inetconv -f -o /var/tmp
100232/10 -> /var/tmp/100232_10-rpc_udp.xml
Importing 100232_10-rpc_udp.xml ...Done
telnet -> /var/tmp/telnet-tcp6.xml
Importing telnet-tcp6.xml ...Done

Example 2: Generating Manifests from an Alternate Input File

The following command specifies a different input file and does not
load the resulting manifests into the smf repository.

# inetconv -n -i /export/test/inet.svcs -o /var/tmp
100232/10 -> /var/tmp/100232_10-rpc_udp.xml
telnet -> /var/tmp/telnet-tcp6.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
manifests.

4
A system error occurred.

FILES

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

default output manifest file name

ATTRIBUTES