[SunHELP] Update: RPC problem after upgrade 2.6 ---> 2.7

[Ives Keith M Cont AFIWC/IOT]

I have found a work around to my problem.

The problem again:
I have a service that registers in rpc but does not start. 

inetd.conf:
tars-rmtload/1   stream   rpc/tcp  wait   topic   /tars/Bin/tars-rmtload
tars-rmtload
notice the owner is "topic" 

/etc/rpc:
tars-rmtload   600000008

rpcinfo -p:
600000008    1    tcp   54509   tars-rmtload

rpcinfo -T tcp camelot  600000008 1
rpcinfo:  RPC:  Timed out
program 600000008 version 1 not available

/var/adm/messages:
.....  rmtload[6898]:  rendezvous_request :  no suitable transport
(this message repeated multiple times)
.....  inetd[363]:  /tars/Bin/tars-rmtload:  Terminated

rpcinfo:
600000008   1   tcp   0.0.0.0.128.12    tars-rmtload   superuser

My work around:

rpcinfo -d  -T  tcp  600000008 1    (delete the regestration)

At this point the process/service is up and running.

rpcinfo -T tcp camelot  600000008 1
program 600000008 version 1 ready and waiting

rpcinfo:
600000008   1   tcp   0.0.0.0.128.12    tars-rmtload   344
notice the owner is now 344 (uid of topic)

BUT, when I reboot I am right back to where I was with superuser owning the
process.

"topic" is not a local account; we use NIS+ and topic has creds.