Hallo, dies ist ein Test.

PWD: /www/data-lst1/unixsoft/unixsoft/kaempfer/.public_html

Running in File Mode
Relative path: ./../../../../../../usr/man/man8/inetconv.8
Real path: /usr/share/man/man8/inetconv.8
Zurück

'\" te .\" Copyright (c) 2011, 2021, Oracle and/or its affiliates. .TH inetconv 8 "17 Mar 2021" "Oracle Solaris 11.4" "System Administration Commands" .SH NAME inetconv \- convert \fBinetd.conf\fR entries into smf service manifests, import them into smf repository .SH SYNOPSIS .LP .nf \fBinetconv\fR \fB-?\fR .fi .LP .nf \fBinetconv\fR [\fB-f\fR] [\fB-n\fR] [\fB-i\fR \fIsrcfile\fR] [\fB-o\fR \fIdestdir\fR] .fi .LP .nf \fBinetconv\fR \fB-e\fR [\fB-n\fR] [\fB-i\fR \fIsrcfile\fR] .fi .SH DESCRIPTION .sp .LP The \fBinetconv\fR utility converts a file containing records of \fBinetd.conf\fR(5) into \fBsmf\fR(7) service manifests, and then import those manifests into the \fBsmf\fR repository. Once the \fBinetd.conf\fR file has been converted, the only way to change aspects of an inet service is to use the \fBinetadm\fR(8) utility. .sp .LP 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: .sp .in +2 .nf \fI<svcname>\fR-\fI<proto>\fR\fB.xml\fR .fi .in -2 .sp .sp .LP The \fI<svcname>\fR token is replaced by the service's name and the \fI<proto>\fR token by the service's protocol. Any slash (\fB/\fR) characters that exist in the source line for the service name or protocol are replaced with underscores (\fB_\fR). .sp .LP The service line is recorded as a property of the converted service. .sp .LP During the conversion process, if a service line is found to be malformed or to be for an internal \fBinetd\fR service, no manifest is generated and that service line is skipped. .sp .LP The input file is left untouched by the conversion process. .SH OPTIONS .sp .LP The following options are supported: .sp .ne 2 .mk .na \fB\fB-?\fR\fR .ad .RS 14n .rt Display a usage message. .RE .sp .ne 2 .mk .na \fB\fB-e\fR\fR .ad .RS 14n .rt Enable \fBsmf\fR services which are listed in the input file. .RE .sp .ne 2 .mk .na \fB\fB-f\fR\fR .ad .RS 14n .rt If a service manifest of the same name as the one to be generated is found in the destination directory, \fBinetconv\fR will overwrite that manifest if this option is specified. Otherwise, an error message is generated and the conversion of that service is not performed. .RE .sp .ne 2 .mk .na \fB\fB-i\fR \fIsrcfile\fR\fR .ad .RS 14n .rt Permits the specification of an alternate input file \fIsrcfile\fR. If this option is not specified, then the \fBinetd.conf\fR(5) file is used as input. .RE .sp .ne 2 .mk .na \fB\fB-n\fR\fR .ad .RS 14n .rt Turns off the auto-import of the manifests generated during the conversion process. Later, if you want to import a generated manifest into the \fBsmf\fR(7) repository, you can do so through the use of the \fBsvccfg\fR(8) utility. .sp If the \fB-e\fR option is specified, the \fB-n\fR option only displays the \fBsmf\fR services that would be enabled. .RE .sp .ne 2 .mk .na \fB\fB-o\fR \fIdestdir\fR\fR .ad .RS 14n .rt Permits the specification of an alternate destination directory \fIdestdir\fR for the generated manifests. If this option is not specified, then the manifests are placed in \fB/lib/svc/manifest/network/rpc\fR, if the service is a RPC service, or \fB/lib/svc/manifest/network\fR otherwise. .RE .SH EXAMPLES .LP \fBExample 1\fR Generating \fBsmf\fR Manifests from \fBinetd.conf\fR .sp .LP The following command generates \fBsmf\fR(7) manifests from newly added lines in \fBinetd.conf\fR(5), places them under \fB/lib/svc/manifest\fR, and then imports them into the \fBsmf\fR repository. Use this command if a network application's installation stores the \fBinetd\fR configuration in \fBinetd.conf\fR instead of \fBsmf\fR. .sp .in +2 .nf # 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 .fi .in -2 .sp .LP \fBExample 2\fR Generating Manifests for Installation Packages .sp .LP The following command retrieves \fBinetd\fR service properties from a workspace build directory and places the resulting manifests into the same directory. It does not load the manifests into \fBsmf\fR. This command may be useful when porting and packaging a network application for later installation on Solaris. .sp .in +2 .nf # BUILDDIR=/export/build/networkapp # inetconv -n -i $BUILDDIR/inet.svcs -o $BUILDDIR networkapp -> /export/build/networkapp/networkapp-tcp.xml .fi .in -2 .sp .SH EXIT STATUS .sp .LP The following exit values are returned: .sp .ne 2 .mk .na \fB\fB0\fR\fR .ad .RS 5n .rt Operation completed successfully (no errors). .RE .sp .ne 2 .mk .na \fB\fB1\fR\fR .ad .RS 5n .rt Invalid options specified. .RE .sp .ne 2 .mk .na \fB\fB2\fR\fR .ad .RS 5n .rt One or more service lines are malformed, and thus no manifest(s) were generated for them. .RE .sp .ne 2 .mk .na \fB\fB3\fR\fR .ad .RS 5n .rt An error occurred importing one or more of the generated manifests. .RE .sp .ne 2 .mk .na \fB\fB4\fR\fR .ad .RS 5n .rt A system error occurred. .RE .SH FILES .sp .ne 2 .mk .na \fB\fB/lib/svc/manifest/network/{rpc}/\fI<svcname>\fR-\fI<proto>\fR.xml\fR\fR .ad .br .sp .6 .RS 4n Default output manifest file name. .RE .SH ATTRIBUTES .sp .LP See \fBattributes\fR(7) for descriptions of the following attributes: .sp .TS tab( ) box; cw(2.75i) |cw(2.75i) lw(2.75i) |lw(2.75i) . ATTRIBUTE TYPE ATTRIBUTE VALUE _ Availability system/network _ Interface Stability Committed .TE .sp .SH SEE ALSO .sp .LP \fBinetd.conf\fR(5), \fBattributes\fR(7), \fBsmf\fR(7), \fBinetadm\fR(8), \fBinetd\fR(8), \fBsvccfg\fR(8)