Sponsored Content
Full Discussion: X
Top Forums UNIX for Dummies Questions & Answers X Post 589 by Neo on Friday 15th of December 2000 04:22:43 PM
Old 12-15-2000
Similar errors are caused by the fact that many implementations of X client/server do not automatically increment to the next available server port. For example, 6000, 6001, 6002, etc. This can cause errors, but I'm not
sure this is your issue.

One way to find out is to use the <B>netstat -c</B> command to watch the connections and ports to the X server(s) and to see what is going on. Also, you can increase the logging level of the X servers to see if you can find out the cause of the error.

If it is a port problem, you can work around this by specifying higher number ports (higher than 6000). Without further information, logfile info, or netstat output, this is the best I have to offer.
 
rpc(n)                                                           Tnm Tcl Extension                                                          rpc(n)

__________________________________________________________________________________________________________________________________________________

NAME
rpc - A simple RPC protocol for Tcl applications. _________________________________________________________________ DESCRIPTION
RPC COMMAND
rpc server port Set up an RPC server listening an port port. This command returns a rpc handle that be used to register Tcl procs that will be exported by a trivial RPC protocol on top of TCP. This RPC mechanism allows us to write cooperating scripts without worrying much about the communication protocol. rpc client host port Connect to the RPC server running on host with port port. The returned client handle can be used to invoke an exported proc on the server host. rpc delete handle Delete a server or a client RPC handle. All connections associated with the handle will be closed. rpc register rpchandle proc Export proc as an RPC callable proc using the server handle rpchandle. Only registered procs can be called by RPC clients. rpc unregister rpchandle proc Remove proc from the list of exported procs on server handle rpchandle. rpc info [rpchandle] Calling rpc info without any arguments returns a list of all rpc handles that have been created using the rpc server and rpc client command. Info about a specific rpc file handle rpchandle is returned by using the optional argument. The result is a list contain- ing the tcp file handle used for the communication and the list of registered commands for a rpc handle and a list of all files that represent connections to an rpc server. This list is empty if rpchandle belongs to a rpc client. rpc# [-async] proc arg1 arg2 ... To invoke a remote procedure proc, use the same syntax as used with a local invocation preceeded by a client rpchandle. The result of the remote procedure call will be returned or an error if the underlying communication channel signals errors. The -async options can be used to invoke proc without waiting for it to complete. The async option will never return a result. SEE ALSO
scotty(1), Tcl(n) AUTHORS
Juergen Schoenwaelder <schoenw@cs.utwente.nl> Tnm rpc(n)
All times are GMT -4. The time now is 08:44 PM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy