inetconv(1m)

1inetconv(1M)            System Administration Commands            inetconv(1M)
2
3
4

NAME

6       inetconv  -  convert  inetd.conf  entries  into  smf service manifests,
7       import them into smf repository
8

SYNOPSIS

10       inetconv -?
11
12
13       inetconv [-f] [-n] [-i srcfile] [-o destdir]
14
15
16       inetconv -e [-n] [-i srcfile]
17
18

DESCRIPTION

20       The  inetconv  utility  converts   a   file   containing   records   of
21       inetd.conf(4) into smf(5) service manifests, and then import those man‐
22       ifests into the smf repository. Once the inetd.conf file has been  con‐
23       verted, the only way to change aspects of an inet service is to use the
24       inetadm(1M) utility.
25
26
27       There is a one-to-one correspondence between  a  service  line  in  the
28       input  file  and  the manifest generated. By default, the manifests are
29       named using the following template:
30
31         <svcname>-<proto>.xml
32
33
34
35       The <svcname> token is replaced by the service's name and  the  <proto>
36       token by the service's protocol. Any slash (/) characters that exist in
37       the source line for the service name  or  protocol  are  replaced  with
38       underscores (_).
39
40
41       The service line is recorded as a property of the converted service.
42
43
44       During  the  conversion  process, if a service line is found to be mal‐
45       formed or to be for an internal inetd service, no manifest is generated
46       and that service line is skipped.
47
48
49       The input file is left untouched by the conversion process.
50

OPTIONS

52       The following options are supported:
53
54       -?            Display a usage message.
55
56
57       -e            Enable smf services which are listed in the input file.
58
59
60       -f            If  a  service manifest of the same name as the one to be
61                     generated is found in the destination directory, inetconv
62                     will overwrite that manifest if this option is specified.
63                     Otherwise, an error message is generated and the  conver‐
64                     sion of that service is not performed.
65
66
67       -i srcfile    Permits the specification of an alternate input file src‐
68                     file.  If  this  option  is  not  specified,   then   the
69                     inetd.conf(4) file is used as input.
70
71
72       -n            Turns off the auto-import of the manifests generated dur‐
73                     ing the conversion process. Later, if you want to  import
74                     a  generated manifest into the smf(5) repository, you can
75                     do so through the use of the svccfg(1M) utility.
76
77                     If the -e option is specified, the -n  option  only  dis‐
78                     plays the smf services that would be enabled.
79
80
81       -o            Permits  the  specification  of  an alternate destination
82                     directory destdir for the generated  manifests.  If  this
83                     option is not specified, then the manifests are placed in
84                     /var/svc/manifest/network/rpc, if the service  is  a  RPC
85                     service, or /var/svc/manifest/network otherwise.
86
87

EXAMPLES

89       Example 1 Generating smf Manifests from inetd.conf
90
91
92       The following command generates smf(5) manifests from inetd.conf(4) and
93       places them in /var/tmp, overwriting any preexisting manifests  of  the
94       same name, and then imports them into the smf repository.
95
96
97         # inetconv -f -o /var/tmp
98         100232/10 -> /var/tmp/100232_10-rpc_udp.xml
99         Importing 100232_10-rpc_udp.xml ...Done
100         telnet -> /var/tmp/telnet-tcp6.xml
101         Importing telnet-tcp6.xml ...Done
102
103
104       Example 2 Generating Manifests from an Alternate Input File
105
106
107       The  following  command  specifies  a different input file and does not
108       load the resulting manifests into the smf repository.
109
110
111         # inetconv -n -i /export/test/inet.svcs -o /var/tmp
112         100232/10 -> /var/tmp/100232_10-rpc_udp.xml
113         telnet -> /var/tmp/telnet-tcp6.xml
114
115

EXIT STATUS

117       The following exit values are returned:
118
119       0    Operation completed successfully (no errors).
120
121
122       1    Invalid options specified.
123
124
125       2    One or more service lines are malformed, and thus  no  manifest(s)
126            were generated for them.
127
128
129       3    An  error  occurred  importing  one or more of the generated mani‐
130            fests.
131
132
133       4    A system error occurred.
134
135

FILES

137       /var/svc/manifest/network/{rpc}/<svcname>-<proto>.xml
138
139           default output manifest file name
140
141

ATTRIBUTES

143       See attributes(5) for descriptions of the following attributes:
144
145
146
147
148       ┌─────────────────────────────┬─────────────────────────────┐
149       │      ATTRIBUTE TYPE         │      ATTRIBUTE VALUE        │
150       ├─────────────────────────────┼─────────────────────────────┤
151       │Availability                 │SUNWcsu                      │
152       ├─────────────────────────────┼─────────────────────────────┤
153       │Interface Stability          │Evolving                     │
154       └─────────────────────────────┴─────────────────────────────┘
155