If it is indeed using ping then on Linux the ping command requires a count "-c 4" to mimic windoze. If the problem is more TCP related then I suggest you use tcpdump/ethereal to analyse what in fact is happening. We have also noted that strange statuses can be returned if ECN is turned on - "cat /proc/sys/net/ipv4/tcp_ecn" is best if = 0.
Ciao Mark -----Original Message----- From: Linux on 390 Port [mailto:LINUX-390@;VM.MARIST.EDU]On Behalf Of Abdullah Al-humaid Sent: 23 October 2002 09:32 To: [EMAIL PROTECTED] Subject: Re: Heartbeat monitor If the method you are talking about is using ping, then they are correct. On windows a ping will be tried 4 times and then it gives up. on linux/unix you need to add the -w flag to the ping command to indicate how long to wait in secs for a response otherwise it will keep trying. hope that helps --- DelRossi Donald <[EMAIL PROTECTED]> wrote: > we are trying to migrate an application that > currently runs on NT to > VM/Linux. This application a type of heartbeat > monitor. It sends a request > to see if a server is available and if not reports > back to the application > owners via email or whatever. The issue is that when > a connection is > requested and fails Linux seems to try forever to > make the connection. They > claim that it does not work this way on NT and want > to scrape the project. > Since I am a proponent of running Linux on s/390 I > would like to see if > there is a way to correct this from a Linux > operating systems view. > > Any help would be appreciated. > > > Thanks, > Don __________________________________________________ Do you Yahoo!? Y! Web Hosting - Let the expert host your web site http://webhosting.yahoo.com/
