08-15-2009
in fact i was using TCP for a fault tolerant system(Redundant Servers). I have 2 servers.One is in standby mode and the other in active mode.Whenever the active server went down, the standby server takes the role.I wrote a small application that is run on both servers. In one it is in server mode and in another it is in client.For this scenario it seems that TCP is not well suited. By your suggestion about "best-effort" delivery mechanism i read internal details of TCP protocol and reached your experience! Thank u.
Any way, i will try ping. it may help to reach my goal.Any suggestion for my redundant servers well appreciated.
Thanks in advance
Behzad
9 More Discussions You Might Find Interesting
1. Shell Programming and Scripting
how to get the list of process running in the server from the local machin n unix ? (3 Replies)
Discussion started by: guhas
3 Replies
2. UNIX for Advanced & Expert Users
Hi,
I was porting ipv4 application to ipv6; i was done with TCP transports. Now i am facing problem with SCTp transport at runtime.
To test SCTP transport I am using following server and client socket programs. Server program runs fine, but client program fails giving Invalid Arguments for... (0 Replies)
Discussion started by: chandrutiptur
0 Replies
3. Solaris
hi everyone.
As a solaris/unix beginner, I am trying a peer-to-peer connection with my Sun and Windows.
Here is my setup:
-Windows XP
-Sun System (Netra T1) which is connected to the console of the WinXP machine.
-Windows XP has wireless connection which enables me to access internet ... (3 Replies)
Discussion started by: graboid888
3 Replies
4. IP Networking
I am looking for advice on a router. I am new to Linux and am trying to use Limewire and Ktorent and can make no connection. Limewire indicates I have a firewall. I have a Linksys router WRK54G and my guess is that is the problem. I have spent hours upon hours trying to get it to work using info... (0 Replies)
Discussion started by: Paul K
0 Replies
5. UNIX for Dummies Questions & Answers
I get this error when I log in through console:
"fatal: Read from socket failed: Connection reset by peer".
Can you tell me what this is and why it happens, and how to stop it? Thank you. (1 Reply)
Discussion started by: iamnew2solaris
1 Replies
6. IP Networking
I need clarification on whether it is okay to set socket options on a listening socket
simultaneously when it is being used in an accept() call?
Following is the scenario:-
-- Task 1 - is executing in a loop - polling a listen socket, lets call it 'fd', (whose file descriptor is global)... (2 Replies)
Discussion started by: jake24
2 Replies
7. IP Networking
Hi,
I am trying to add a static route in one of 3 server (S3) so that I can access the main application server (S1). But problem is, the server (S3) where I am trying to add static route is connected with another server (S2) which is in same private network of application server (S1).
I have... (9 Replies)
Discussion started by: ImranBD
9 Replies
8. UNIX for Advanced & Expert Users
Hello,
I have recently updated my AIX machine from version 6.1.7.5 to 6.1.9.1 and i noticed that the errpt of the server is full of ssh messages like the one below:
sshdprocess_id>]: fatal: Read from socket failed: Connection reset by peer
Does anyone knows if this a known bug of the ssh... (15 Replies)
Discussion started by: omonoiatis9
15 Replies
9. AIX
Hi,
Can you explain me step by step how can add my aix 6.1 to windows network.
Thans:rolleyes: (5 Replies)
Discussion started by: tatab355
5 Replies
LEARN ABOUT ULTRIX
rpc_allow_remote_shutdown
rpc_allow_remote_shutdown(3ncs) rpc_allow_remote_shutdown(3ncs)
Name
rpc_allow_remote_shutdown - allow or disallow remote shutdown of a server (server only)
Syntax
#include <idl/c/rpc.h>
void rpc_$allow_remote_shutdown(allow, checkproc, status)
unsigned long allow;
rpc_$shut_check_fn_t checkproc;
status_$t *status;
Arguments
allow A value indicating `false' if zero, `true' otherwise.
checkproc A pointer to a Boolean function.
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 allows or disallows remote callers to shut down a server using
By default, servers do not allow remote shutdown via If a server calls with allow true (not zero) and checkproc nil, then remote shutdown
will be allowed. If allow is true and checkproc is not nil, then when a remote shutdown request arrives, the function denoted by checkproc
is called and the shutdown is allowed if the function returns true. If allow is false (zero), remote shutdown is disallowed.
Diagnostics
This section lists status codes for errors returned by this routine in
rpc_$not_in_call An internal error.
rpc_$you_crashed This error can occur if a server has crashed and restarted. A client RPC runtime library sends the error to the server
if the client makes a remote procedure call before the server crashes, then receives a response after the server
restarts.
rpc_$proto_error An internal protocol error.
Files
See Also
intro(3ncs), rpc_shutdown(3ncs), rrpc_shutdown(3ncs)
rpc_allow_remote_shutdown(3ncs)