Sponsored Content
Top Forums Programming Configure ONC RPC clnt_create Timeout Post 302395687 by jim mcnamara on Tuesday 16th of February 2010 04:43:31 PM
Old 02-16-2010
clnt_create_timed() ?
 

10 More Discussions You Might Find Interesting

1. Programming

Rpc

Hello, I would like to do a program (in C) on which I would have to call 3 or more executables using execl command. But if the executables are situated on another machine say Y and I do a programe on the machine X, is it possible to invoke those executables (binaries) from the other machine... (1 Reply)
Discussion started by: driki
1 Replies

2. UNIX for Dummies Questions & Answers

RPC service

Hi All, How can I add RPC service in SCO 5.0.7. I did not find in the sco cd please help me Alice (0 Replies)
Discussion started by: alisevA3
0 Replies

3. Red Hat

RPC Timeout

I have a RHEL 2.1 machine that I am trying to get to mount a remote nfs filesystem. Both servers have 2 network interfaces. My linux machine can mount the filesystem through one interface with no problems but if I switch over and try to mount it through the other interface using a totally... (1 Reply)
Discussion started by: darren.wyatt
1 Replies

4. Programming

C Shell RPC help

Hello everyone, I am writing a rpc program, I have put the server program on a directory in another computer and i run the client program from my computer. I want that when i call a function in the server program it will have to execute a shell script and the retruning of the shell script be... (6 Replies)
Discussion started by: ermalguni
6 Replies

5. Solaris

RPC: Rpcbind failure - RPC: Timed out

while i trying to mount from NAS i have this messages mount -F nfs -o rw 172.16.110.13:/tremabkup /tremabkup nfs mount: 172.16.110.13: : RPC: Rpcbind failure - RPC: Timed out nfs mount: retrying: /tremabkup nfs mount: 172.16.110.13: : RPC: Rpcbind failure - RPC: Timed out nfs mount:... (2 Replies)
Discussion started by: thecobra151
2 Replies

6. Solaris

Solaris: clnt_create fails on solaris x86

Hi, I am facing an issue with Solaris x86 machine Machine Details: uname -a SunOS sol10-64 5.10 Generic_137138-09 i86pc i386 i86pc .............................. Description: I am trying to register a programm with proramm ID 300760 with version number 1, and tryint to create a... (0 Replies)
Discussion started by: DivakarAdari
0 Replies

7. Solaris

Error : "RPC: Rpcbind failure - RPC: Timed out"

Hello I am having an issue with a server SUN FIRE T2000 (Solaris 10). First of all the server didn't boot normaly so I did a full restoration of the file systems. Now the server boot, most of the services are available (not all the services), but I keep on seeing RPC: Rpcbind failure -... (4 Replies)
Discussion started by: feg
4 Replies

8. Solaris

RPC: Rpcbind failure - RPC: Timed out error (solaris)

C: Rpcbind failure - RPC: Timed out error (solaris) hello an nfs server on my sun fire v440 is not responding , i get the error bellow and lots of my networking services are not reponding, please helppppp its an emergency RPC: Rpcbind failure - RPC: Timed out i also get NFS server... (2 Replies)
Discussion started by: feg
2 Replies

9. Solaris

nfs mount: RPC: Rpcbind failure - RPC: Timed out

Fails to mount the server (10.125.224.22) during installation of a software on client, throwing the below error: nfs mount: 10.125.224.22: : RPC: Rpcbind failure - RPC: Timed out nfs mount: retrying: /cdrom This happened after complete shutdown of the lab. The server came up fine but most... (1 Reply)
Discussion started by: frintocf
1 Replies

10. HP-UX

RPC Error

Hi All, I am receiving RPC-Error 5 and sometimes RPC-Error 2 in my Hp-Ux servers. I have tried to kill and restart again.. Again same errors. Sometimes RPC process going down. Due to this other applications are not working in Hp ux servers. Kindly share some ideas for root cause... Or... (2 Replies)
Discussion started by: jakmani
2 Replies
RPC_CLNT_CREATE(3)					   BSD Library Functions Manual 					RPC_CLNT_CREATE(3)

NAME
rpc_clnt_create, clnt_control, clnt_create, clnt_create_timed, clnt_create_vers, clnt_create_vers_timed, clnt_destroy, clnt_dg_create, clnt_pcreateerror, clnt_raw_create, clnt_spcreateerror, clnt_tli_create, clnt_tp_create, clnt_tp_create_timed, clnt_vc_create, rpc_createerr -- library routines for dealing with creation and manipulation of CLIENT handles LIBRARY
Standard C Library (libc, -lc) SYNOPSIS
#include <rpc/rpc.h> bool_t clnt_control(CLIENT *clnt, const u_int req, char *info); CLIENT * clnt_create(const char * host, const rpcprog_t prognum, const rpcvers_t versnum, const char *nettype); CLIENT * clnt_create_timed(const char * host, const rpcprog_t prognum, const rpcvers_t versnum, const char *nettype, const struct timeval *timeout); CLIENT * clnt_create_vers(const char * host, const rpcprog_t prognum, rpcvers_t *vers_outp, const rpcvers_t vers_low, const rpcvers_t vers_high, const char *nettype); CLIENT * clnt_create_vers_timed(const char * host, const rpcprog_t prognum, rpcvers_t *vers_outp, const rpcvers_t vers_low, const rpcvers_t vers_high, const char *nettype, const struct timeval *timeout); void clnt_destroy(CLIENT *clnt); CLIENT * clnt_dg_create(const int fildes, const struct netbuf *svcaddr, const rpcprog_t prognum, const rpcvers_t versnum, const u_int sendsz, const u_int recvsz); void clnt_pcreateerror(const char *s); char * clnt_spcreateerror(const char *s); CLIENT * clnt_raw_create(const rpcprog_t prognum, const rpcvers_t versnum); CLIENT * clnt_tli_create(const int fildes, const struct netconfig *netconf, struct netbuf *svcaddr, const rpcprog_t prognum, const rpcvers_t versnum, const u_int sendsz, const u_int recvsz); CLIENT * clnt_tp_create(const char * host, const rpcprog_t prognum, const rpcvers_t versnum, const struct netconfig *netconf); CLIENT * clnt_tp_create_timed(const char * host, const rpcprog_t prognum, const rpcvers_t versnum, const struct netconfig *netconf, const struct timeval *timeout); CLIENT * clnt_vc_create(const int fildes, const struct netbuf *svcaddr, const rpcprog_t prognum, const rpcvers_t versnum, u_int sendsz, u_int recvsz); DESCRIPTION
RPC library routines allow C language programs to make procedure calls on other machines across the network. First a CLIENT handle is cre- ated and then the client calls a procedure to send a request to the server. On receipt of the request, the server calls a dispatch routine to perform the requested service, and then sends a reply. Routines clnt_control() A function macro to change or retrieve various information about a client object. The req argument indicates the type of operation, and info is a pointer to the information. For both connectionless and connection-oriented transports, the supported values of req and their argument types and what they do are: CLSET_TIMEOUT struct timeval * set total timeout CLGET_TIMEOUT struct timeval * get total timeout Note: if you set the timeout using clnt_control(), the timeout argument passed by clnt_call() is ignored in all subsequent calls. Note: If you set the timeout value to 0, clnt_control() immediately returns an error (RPC_TIMEDOUT). Set the timeout argument to 0 for batching calls. CLGET_SVC_ADDR struct netbuf * get servers address CLGET_FD int * get fd from handle CLSET_FD_CLOSE void close fd on destroy CLSET_FD_NCLOSE void do not close fd on destroy CLGET_VERS uint32_t * get RPC program version CLSET_VERS uint32_t * set RPC program version CLGET_XID uint32_t * get XID of previous call CLSET_XID uint32_t * set XID of next call The following operations are valid for connectionless transports only: CLSET_RETRY_TIMEOUT struct timeval * set the retry timeout CLGET_RETRY_TIMEOUT struct timeval * get the retry timeout CLSET_CONNECT int * use connect(2) The retry timeout is the time that RPC waits for the server to reply before retransmitting the request. The clnt_control() function returns TRUE on success and FALSE on failure. clnt_create() Generic client creation routine for program prognum and version versnum. The host argument identifies the name of the remote host where the server is located. The nettype argument indicates the class of transport protocol to use. The transports are tried in left to right order in NETPATH environment variable or in top to bottom order in the netconfig database. The clnt_create() function tries all the transports of the nettype class available from the NETPATH environment variable and the netconfig database, and chooses the first successful one. A default timeout is set and can be modified using clnt_control(). This routine returns NULL if it fails. The clnt_pcreateerror() routine can be used to print the reason for failure. Note: clnt_create() returns a valid client handle even if the particular version number supplied to clnt_create() is not registered with the rpcbind(8) service. This mismatch will be discovered by a clnt_call() later (see rpc_clnt_calls(3)). clnt_create_timed() Generic client creation routine which is similar to clnt_create() but which also has the additional argument timeout that specifies the maximum amount of time allowed for each transport class tried. In all other respects, the clnt_create_timed() call behaves exactly like the clnt_create() call. clnt_create_vers() Generic client creation routine which is similar to clnt_create() but which also checks for the version availability. The host argument identifies the name of the remote host where the server is located. The nettype argument indicates the class transport protocols to be used. If the routine is successful it returns a client handle created for the highest version between vers_low and vers_high that is supported by the server. The vers_outp argument is set to this value. That is, after a successful return vers_low <= *vers_outp <= vers_high. If no version between vers_low and vers_high is supported by the server then the routine fails and returns NULL. A default timeout is set and can be modified using clnt_control(). This routine returns NULL if it fails. The clnt_pcreateerror() routine can be used to print the reason for failure. Note: clnt_create() returns a valid client handle even if the particular version number supplied to clnt_create() is not registered with the rpcbind(8) service. This mismatch will be dis- covered by a clnt_call() later (see rpc_clnt_calls(3)). However, clnt_create_vers() does this for you and returns a valid handle only if a version within the range supplied is supported by the server. clnt_create_vers_timed() Generic client creation routine which is similar to clnt_create_vers() but which also has the additional argument timeout that spec- ifies the maximum amount of time allowed for each transport class tried. In all other respects, the clnt_create_vers_timed() call behaves exactly like the clnt_create_vers() call. clnt_destroy() A function macro that destroys the client's RPC handle. Destruction usually involves deallocation of private data structures, including clnt itself. Use of clnt is undefined after calling clnt_destroy(). If the RPC library opened the associated file descriptor, or CLSET_FD_CLOSE was set using clnt_control(), the file descriptor will be closed. The caller should call auth_destroy(clnt->cl_auth) (before calling clnt_destroy()) to destroy the associated AUTH structure (see rpc_clnt_auth(3)). clnt_dg_create() This routine creates an RPC client for the remote program prognum and version versnum; the client uses a connectionless transport. The remote program is located at address svcaddr. The fildes argument is an open and bound file descriptor. This routine will resend the call message in intervals of 15 seconds until a response is received or until the call times out. The total time for the call to time out is specified by clnt_call() (see clnt_call() in rpc_clnt_calls(3)). The retry time out and the total time out periods can be changed using clnt_control(). The user may set the size of the send and receive buffers with the sendsz and recvsz arguments; values of 0 choose suitable defaults. This routine returns NULL if it fails. clnt_pcreateerror() Print a message to standard error indicating why a client RPC handle could not be created. The message is prepended with the string s and a colon, and appended with a newline. clnt_spcreateerror() Like clnt_pcreateerror(), except that it returns a string instead of printing to the standard error. A newline is not appended to the message in this case. Warning: returns a pointer to a buffer that is overwritten on each call. clnt_raw_create() This routine creates an RPC client handle for the remote program prognum and version versnum. The transport used to pass messages to the service is a buffer within the process's address space, so the corresponding RPC server should live in the same address space; (see svc_raw_create() in rpc_svc_create(3)). This allows simulation of RPC and measurement of RPC overheads, such as round trip times, without any kernel or networking interference. This routine returns NULL if it fails. The clnt_raw_create() function should be called after svc_raw_create(). clnt_tli_create() This routine creates an RPC client handle for the remote program prognum and version versnum. The remote program is located at address svcaddr. If svcaddr is NULL and it is connection-oriented, it is assumed that the file descriptor is connected. For con- nectionless transports, if svcaddr is NULL, RPC_UNKNOWNADDR error is set. The fildes argument is a file descriptor which may be open, bound and connected. If it is RPC_ANYFD, it opens a file descriptor on the transport specified by netconf. If fildes is RPC_ANYFD and netconf is NULL, a RPC_UNKNOWNPROTO error is set. If fildes is unbound, then it will attempt to bind the descriptor. The user may specify the size of the buffers with the sendsz and recvsz arguments; values of 0 choose suitable defaults. Depending upon the type of the transport (connection-oriented or connectionless), clnt_tli_create() calls appropriate client creation rou- tines. This routine returns NULL if it fails. The clnt_pcreateerror() routine can be used to print the reason for failure. The remote rpcbind service (see rpcbind(8)) is not consulted for the address of the remote service. clnt_tp_create() Like clnt_create() except clnt_tp_create() tries only one transport specified through netconf. The clnt_tp_create() function cre- ates a client handle for the program prognum, the version versnum, and for the transport specified by netconf. Default options are set, which can be changed using clnt_control() calls. The remote rpcbind service on the host host is consulted for the address of the remote service. This routine returns NULL if it fails. The clnt_pcreateerror() routine can be used to print the reason for failure. clnt_tp_create_timed() Like clnt_tp_create() except clnt_tp_create_timed() has the extra argument timeout which specifies the maximum time allowed for the creation attempt to succeed. In all other respects, the clnt_tp_create_timed() call behaves exactly like the clnt_tp_create() call. clnt_vc_create() This routine creates an RPC client for the remote program prognum and version versnum; the client uses a connection-oriented trans- port. The remote program is located at address svcaddr. The fildes argument is an open and bound file descriptor. The user may specify the size of the send and receive buffers with the sendsz and recvsz arguments; values of 0 choose suitable defaults. This routine returns NULL if it fails. The address svcaddr should not be NULL and should point to the actual address of the remote pro- gram. The clnt_vc_create() function does not consult the remote rpcbind service for this information. struct rpc_createerr rpc_createerr; A global variable whose value is set by any RPC client handle creation routine that fails. It is used by the routine clnt_pcreateerror() to print the reason for the failure. SEE ALSO
rpc(3), rpc_clnt_auth(3), rpc_clnt_calls(3), rpcbind(8) BSD
May 7, 1993 BSD
All times are GMT -4. The time now is 04:58 AM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy