Something like this came across an internal alias yesterday. I tried to reproduce it, and this is what I got. Posting here for a wider audience.
I copied /usr/sbin/in.ftpd to /scratch/ftpd, we'll pretend the latter is some different ftpd binary. Here's the content of my file "foo": ftp stream tcp nowait root /scratch/ftpd -a -a -u 002 # inetconv -i ./foo ftp -> /var/svc/manifest/network/ftp-tcp.xml Importing ftp-tcp.xml ...Done # svcs -a|grep ftp online 11:03:19 svc:/network/ftp:default <-out-of-the-box default online 15:48:23 svc:/network/ftp/tcp:default <-my new import # svcprop -p inetd/proto network/ftp <-out-of-the-box default tcp6 # svcprop -p inetd/proto network/ftp/tcp:default <-my new import tcp Removed new import, deleted manifest, put things back the way they were. # inetconv -e -i ./foo svc:/network/ftp:default will exec /scratch/ftpd -a -u 002 svc:/network/ftp:default will have an arg0 of -a svc:/network/ftp:default enabled # svcs -a|grep ftp online 11:03:19 svc:/network/ftp:default # svcprop -p inetd/proto ftp tcp6 The 2nd usage overwrote my out-of-the-box-default, did not create a new service, and didn't honor what's in my "foo". I don't understand the behavior of switch "-e", the man page is not clear, can someone explain? CT