Linux and UNIX Man Pages

Linux & Unix Commands - Search Man Pages

rpc_clear_server_binding(3ncs) [ultrix man page]

rpc_clear_server_binding(3ncs)											    rpc_clear_server_binding(3ncs)

Name
       rpc_clear_server_binding - unset the binding of an RPC handle to a server (client only)

Syntax
       #include <idl/c/rpc.h>

       void rpc_$clear_server_binding(handle, status)
       handle_t handle;
       status_$t *status;

Arguments
       handle		   The RPC handle whose binding is being cleared.

       status		   The completion status.  If the completion status returned in is equal to status_$ok , then the routine that supplied it
			   was successful.

Description
       The routine removes the association between an RPC handle and a particular server (that is, a particular port number), but does not  remove
       the associations with an object and with a host (that is, a network address).  This call replaces a fully bound handle with a bound-to-host
       handle.	A bound-to-host handle identifies an object located on a particular host but does not identify a server exporting an interface	to
       the object.

       If  a  client  uses  a bound-to-host handle to make a remote procedure call, the call is sent to the Local Location Broker (LLB) forwarding
       port at the host identified by the handle.  If the call's interface and the object identified by the handle are both  registered  with  the
       host's  LLB, the LLB forwards the request to the registering server.  When the client RPC runtime library receives a response, it binds the
       handle to the server.  Subsequent remote procedure calls that use this handle are then sent directly to the bound server's port.

       The routine is useful for client error recovery when a server dies.  The port that a server uses when it restarts is  not  necessarily  the
       same port that it used previously; therefore, the binding that the client was using may not be correct.	This routine enables the client to
       unbind from the dead server while retaining the binding to the host.  When the client sends a request, the binding is automatically set	to
       the server's new port.

Diagnostics
       This section lists status codes for errors returned by this routine in

       rpc_$not_in_call    An internal error.

       rpc_$proto_error    An internal protocol error.

Files
See Also
       intro(3ncs), rpc_bind(3ncs), rpc_clear_binding(3ncs), rpc_set_binding(3ncs)

														    rpc_clear_server_binding(3ncs)

Check Out this Related Man Page

rpc_use_family(3ncs)													      rpc_use_family(3ncs)

Name
       rpc_use_family - create a socket of a specified address family for a remote procedure call (RPC) server (server only)

Syntax
       #include <idl/c/rpc.h>

       void rpc_$use_family(family, sockaddr, slength, status)
       unsigned long family;
       socket_$addr_t *sockaddr;
       unsigned long *slength;
       status_$t *status;

Arguments
       family	      The address family of the socket to be created.  The value must be one of socket_$internet or socket_$unspec.

       sockaddr       The socket address of the socket on which the server will listen.

       slength	      The length, in bytes, of sockaddr.

       status	      The  completion status.  If the completion status returned in is equal to status_$ok , then the routine that supplied it was
		      successful.

Description
       The routine creates a socket for a server without specifying its port number.  The RPC runtime software assigns a port number.  If a server
       must listen on a particular well-known port, use to create the socket.

       A  server listens on one socket per address family, regardless of how many interfaces that it exports.  Therefore, servers should make this
       call once per supported address family.

Examples
       The following statement creates a server's socket:
       rpc_$use_family (family, &saddr, &slen, &status);

Diagnostics
       This section lists status codes for errors returned by this routine in

       rpc_$cant_create_sock
			   The RPC runtime library was unable to create a socket.

       rpc_$not_in_call    An internal error.

       rpc_$proto_error    An internal protocol error.

       rpc_$too_many_sockets
			   The server is trying to use more than the maximum number of sockets that is allowed; it has called or too many times.

       rpc_$addr_in_use    The address and port specified in an routine are already in use.  This is caused by multiple calls  to  with  the  same
			   well-known port.

Files
See Also
       intro(3ncs), rpc_use_family_wk(3ncs)

															      rpc_use_family(3ncs)
Man Page