What inetd services causes port to be opened?

Question

Hello.
I'd like to find out, what inetd-controlled service is causing a certain port to be opened by inetd. In particular, I'd like to know, why port 6112 is opened.
adm@winds02 ~ $ getent services 6112
dtspc                6112/tcpThis means, that "dtspc" is assigned port 6112, doesn't it?
adm@winds02 ~ $ inetadm | grep dts
enabled   maintenance    svc:/network/dtspc/tcp:default
adm@winds02 ~ $ inetadm -l svc:/network/dtspc/tcp:default
SCOPE    NAME=VALUE
         name="dtspc"
         endpoint_type="stream"
         proto="tcp"
         isrpc=FALSE
         wait=FALSE
         exec="/usr/dt/bin/dtspcd"
         arg0="/usr/dt/bin/dtspcd"
         user="root"
default  bind_addr=""
default  bind_fail_max=-1
default  bind_fail_interval=-1
default  max_con_rate=-1
default  max_copies=-1
default  con_rate_offline=-1
default  failrate_cnt=40
default  failrate_interval=60
default  inherit_env=TRUE
default  tcp_trace=FALSE
default  tcp_wrappers=FALSENow I'm disabling dtspc and run pcp <http://www.unix.ms/pcp/> again:
adm@winds02 ~ $ sudo bin/./pcp -p 6112
PID     Process Name and Port
274     /usr/lib/inet/inetd     6112
        sockname: AF_INET 0.0.0.0  port: 6112
1546    /usr/lib/inet/inetd     6112
        sockname: AF_INET 0.0.0.0  port: 6112
1595    /usr/lib/inet/inetd     6112
        sockname: AF_INET 0.0.0.0  port: 6112
_________________________________________________________Question: Why is port 6112 still open?
adm@winds02 ~ $ inetadm
ENABLED   STATE          FMRI
disabled  disabled       svc:/application/x11/xfs:default
enabled   online         svc:/application/font/stfsloader:default
disabled  disabled       svc:/application/print/rfc1179:default
enabled   online         svc:/network/rpc/gss:default
disabled  disabled       svc:/network/rpc/cde-calendar-manager:default
enabled   online         svc:/network/rpc/cde-ttdbserver:tcp
enabled   online         svc:/network/rpc/ocfserv:default
disabled  disabled       svc:/network/rpc/smserver:default
disabled  disabled       svc:/network/rpc/mdcomm:default
enabled   online         svc:/network/rpc/meta:default
disabled  disabled       svc:/network/rpc/metamed:default
enabled   online         svc:/network/rpc/metamh:default
disabled  disabled       svc:/network/rpc/rex:default
enabled   online         svc:/network/rpc/rstat:default
disabled  disabled       svc:/network/rpc/rusers:default
disabled  disabled       svc:/network/rpc/spray:default
disabled  disabled       svc:/network/rpc/wall:default
enabled   online         svc:/network/security/ktkt_warn:default
disabled  disabled       svc:/network/security/krb5_prop:default
disabled  disabled       svc:/network/swat:default
enabled   online         svc:/network/cde-spc:default
enabled   online         svc:/network/tname:default
enabled   online         svc:/network/telnet:default
enabled   online         svc:/network/nfs/rquota:default
disabled  disabled       svc:/network/uucp:default
disabled  disabled       svc:/network/chargen:dgram
disabled  disabled       svc:/network/chargen:stream
disabled  disabled       svc:/network/daytime:dgram
disabled  disabled       svc:/network/daytime:stream
disabled  disabled       svc:/network/discard:dgram
disabled  disabled       svc:/network/discard:stream
disabled  disabled       svc:/network/echo:dgram
disabled  disabled       svc:/network/echo:stream
disabled  disabled       svc:/network/time:dgram
disabled  disabled       svc:/network/time:stream
enabled   online         svc:/network/ftp:default
disabled  disabled       svc:/network/comsat:default
disabled  disabled       svc:/network/finger:default
disabled  disabled       svc:/network/login:eklogin
disabled  disabled       svc:/network/login:klogin
enabled   online         svc:/network/login:rlogin
enabled   online         svc:/network/rexec:default
enabled   online         svc:/network/shell:default
disabled  disabled       svc:/network/shell:kshell
disabled  disabled       svc:/network/talk:default
disabled  disabled       svc:/network/stdiscover:default
disabled  disabled       svc:/network/stlisten:default
enabled   online         svc:/network/rpc-100083_1/rpc_tcp:default
enabled   online         svc:/network/rpc-100235_1/rpc_ticotsord:default
disabled  disabled       svc:/network/dtspc/tcp:default
enabled   online         svc:/network/rpc-100068_2-5/rpc_udp:default
disabled  disabled       svc:/network/bpcd/tcp:default
disabled  disabled       svc:/network/vnetd/tcp:default
disabled  disabled       svc:/network/vopied/tcp:default
disabled  disabled       svc:/network/bpjava-msvc/tcp:default
disabled  disabled       svc:/network/swat/tcp:defaultThanks a lot,
Alexander

Answer 1

Darren_Dunham,
Even if something's binding to port 6112 in a ngz, why should that matter to the global zone? After all, those are different IPs, and binding means, that something binds to an IP+Port combination (or NIC+Port).So they are. But Zones have a different concept of "ADDR_ANY" than the global zone does, and this difference is not readily apparent in 'pfiles' output.
So a ngz can run an application that binds to ADDR_ANY (0.0.0.0), but it's really bound only to the IP addresses visible inside the zone.
The thing is that from the global zone, 'ps' will see all the processes (including those in ngzs), and 'pfiles' will show that both processes are bound to the same port (and not via a specific IP address).
This document below is really focusing more on exclusive IP zones, but if you look at page 7 and page 8, it shows two normal processes joining a standard TCP stack and two processes in separate shared-IP zones using their own TCP stacks (with the crucial difference that the app can bind to 0.0.0.0 and get different IPs)
http://blogs.sun.com/aland/resource/ipinstances-svosug.pdf
Darren