Michael Hunter wrote: >> I don't understand the behavior of switch "-e", the man page is not >> clear, can someone explain? > > The interesting code is here: > http://cvs.opensolaris.org/source/xref/onnv/onnv-gate/usr/src/cmd/cmd-inet/usr.sbin/inetconv/inetconv.c#1470 > > '-e' just uses the inet configuration file as a list of services to > enable. it doesn't do any conversion (1487). I agree the man page > isn't all that clear. File a bug against it.
It would not be such a big deal if it merely enables; there's partial importing and overwriting as well: root at zone1~> inetconv -e -i /foo svc:/network/ftp:default will exec /scratch/ftpd -a -u 002 svc:/network/ftp> listprop inetd_start/* inetd_start/timeout_seconds count 0 inetd_start/type astring method inetd_start/use_profile boolean false inetd_start/user astring root inetd_start/working_directory astring :default inetd_start/exec astring "/scratch/ftpd -a -u 002" inetd_start/arg0 astring -a I can't imagine when I would use inetconv -e, I already have inetadm -e, and svcadm enable, and the behavior of -e -i is just weird. I can't file a bug against the man page because I don't know what the man page should say. I believe inetconv by default enables a newly converted service, having the line uncommented in inetd.conf means you want the service to run to begin with. Was -e and -i ever intended to be used together? Can we just get rid of -e? I don't need three ON switches. CT
