Bad news. UniAdmin uses uvcs (UniObjects) to connect. You can't achieve what you want.
When a client connects via UniRPC it requests access to some particular service. The unirpcd daemon/service checks in unirpcservices for the executable, authorised nodes, protocol and default timeout. You might try '' in field number 3 to block all nodes. UV/Net allows UniVerse processes on one system to update records on another (this one) via a uvnet slave which takes care of local (memory-based) locks. The uvdrsrvr service allows subscribing nodes to connect to published updates within UniVerse Database Replication. The uvserver service is for the UCI, which handles inbound SQL functions. UniVerse ODBC ends up using this service. So do BCI requests from this or other nodes. The uvcs (UniVerse Common Server) is the back end for UniObjects (as you can see it starts an instance of uvapi_server (each of which may fork uvapi_slave processes). The uvfilefix service is for running the file repair tool (fixtool) from a client, primarily the UniAdmin client. The udcs (UniData Common Server) is UniData's analogue of the UniVerse Common Server. The defcs entry indicates whether uvcs or udcs (or even dscs (DataStage)) is the default common server. I'll leave it to someone with more UniData knowledge than mine to respond to what udadmin, udadmin60, udserver (analogue of uvserver?), unirep60 (database replication?) and rmconn60 are. ------- u2-users mailing list [email protected] To unsubscribe please visit http://listserver.u2ug.org/
