<?xml version="1.0" encoding="UTF-8"?>
<rss xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#" xmlns:taxo="http://purl.org/rss/1.0/modules/taxonomy/" version="2.0">
  <channel>
    <title>topic Re: Checking Network Connectivity in Operating System - HP-UX</title>
    <link>https://community.hpe.com/t5/operating-system-hp-ux/checking-network-connectivity/m-p/2559292#M918166</link>
    <description>Hi Joseph:&lt;BR /&gt;&lt;BR /&gt;Why not do a simple shell 'ping'?&lt;BR /&gt;&lt;BR /&gt;...JRF...</description>
    <pubDate>Tue, 31 Jul 2001 14:36:11 GMT</pubDate>
    <dc:creator>James R. Ferguson</dc:creator>
    <dc:date>2001-07-31T14:36:11Z</dc:date>
    <item>
      <title>Checking Network Connectivity</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/checking-network-connectivity/m-p/2559291#M918165</link>
      <description>I am writing a C program that issues a remsh command to a server, retrieves some data and processes it.&lt;BR /&gt;&lt;BR /&gt;Is there any any way of checking the network connectivity using the system calls as remsh can take a lot longer to time out.&lt;BR /&gt;&lt;BR /&gt;Regards,&lt;BR /&gt;&lt;BR /&gt;Joseph.</description>
      <pubDate>Tue, 31 Jul 2001 14:28:14 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/checking-network-connectivity/m-p/2559291#M918165</guid>
      <dc:creator>Joseph A Benaiah_1</dc:creator>
      <dc:date>2001-07-31T14:28:14Z</dc:date>
    </item>
    <item>
      <title>Re: Checking Network Connectivity</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/checking-network-connectivity/m-p/2559292#M918166</link>
      <description>Hi Joseph:&lt;BR /&gt;&lt;BR /&gt;Why not do a simple shell 'ping'?&lt;BR /&gt;&lt;BR /&gt;...JRF...</description>
      <pubDate>Tue, 31 Jul 2001 14:36:11 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/checking-network-connectivity/m-p/2559292#M918166</guid>
      <dc:creator>James R. Ferguson</dc:creator>
      <dc:date>2001-07-31T14:36:11Z</dc:date>
    </item>
    <item>
      <title>Re: Checking Network Connectivity</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/checking-network-connectivity/m-p/2559293#M918167</link>
      <description>Hi:&lt;BR /&gt;&lt;BR /&gt;Unless you want to go to the trouble of setting up sockets, probably the easist method is to do a popen("ping remote_host -n 1","r")&lt;BR /&gt;and parse the results.&lt;BR /&gt;&lt;BR /&gt;Clay</description>
      <pubDate>Tue, 31 Jul 2001 14:37:29 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/checking-network-connectivity/m-p/2559293#M918167</guid>
      <dc:creator>A. Clay Stephenson</dc:creator>
      <dc:date>2001-07-31T14:37:29Z</dc:date>
    </item>
    <item>
      <title>Re: Checking Network Connectivity</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/checking-network-connectivity/m-p/2559294#M918168</link>
      <description>Hi (again) Joesph:&lt;BR /&gt;&lt;BR /&gt;You could verify connectivity with one 'ping' with this script.  We look for a zero percent packet loss to confirm connectivity.  The argument to the script constitutes an IPaddress or hostname:&lt;BR /&gt;&lt;BR /&gt;#!/usr/bin/sh&lt;BR /&gt;typeset HOST=${1:-localhost}&lt;BR /&gt;ping $HOST -n 1|grep -q "0%"&lt;BR /&gt;if [ $? -eq 0 ]&lt;BR /&gt;then&lt;BR /&gt;  echo "$HOST is alive"&lt;BR /&gt;else&lt;BR /&gt;  echo "$HOST isn't responding"&lt;BR /&gt;fi&lt;BR /&gt;#.end.&lt;BR /&gt;&lt;BR /&gt;...JRF...</description>
      <pubDate>Tue, 31 Jul 2001 15:03:58 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/checking-network-connectivity/m-p/2559294#M918168</guid>
      <dc:creator>James R. Ferguson</dc:creator>
      <dc:date>2001-07-31T15:03:58Z</dc:date>
    </item>
    <item>
      <title>Re: Checking Network Connectivity</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/checking-network-connectivity/m-p/2559295#M918169</link>
      <description>Hi again Joseph:&lt;BR /&gt;&lt;BR /&gt;Since you specifically mentioned C, I had a standard signal handler I use and I simply modified it for you specific needs. The timeout for ping can vary so this way you can set the timeout to any value you choose.&lt;BR /&gt;&lt;BR /&gt;The function returns 0 is the ping is good and non-zero otherwise.&lt;BR /&gt;&lt;BR /&gt;Clay</description>
      <pubDate>Tue, 31 Jul 2001 15:35:42 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/checking-network-connectivity/m-p/2559295#M918169</guid>
      <dc:creator>A. Clay Stephenson</dc:creator>
      <dc:date>2001-07-31T15:35:42Z</dc:date>
    </item>
    <item>
      <title>Re: Checking Network Connectivity</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/checking-network-connectivity/m-p/2559296#M918170</link>
      <description>Thanks for such a quick response, I will probably have to set up a socket connection as I can ping a server, remsh, rexec, rlogin and telnet fails.&lt;BR /&gt;&lt;BR /&gt;I will refer to my network programming book and see if there is a quick method for testing a remote connection.&lt;BR /&gt;&lt;BR /&gt;If I was testing this from a shell, I would run:&lt;BR /&gt;&lt;BR /&gt;if remsh ${host} "uptime" 2&amp;gt;&amp;amp;1 | grep -v -q "load average"&lt;BR /&gt;then&lt;BR /&gt;echo "Cannot remsh to ${host}"&lt;BR /&gt;exit&lt;BR /&gt;fi&lt;BR /&gt;&lt;BR /&gt;Cheers,&lt;BR /&gt;&lt;BR /&gt;Joseph.&lt;BR /&gt;&lt;BR /&gt;</description>
      <pubDate>Wed, 01 Aug 2001 08:17:48 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/checking-network-connectivity/m-p/2559296#M918170</guid>
      <dc:creator>Joseph A Benaiah_1</dc:creator>
      <dc:date>2001-08-01T08:17:48Z</dc:date>
    </item>
  </channel>
</rss>

