Re: Mount point - timeout
- From: Steve <Steve@xxxxxxxxxx>
- Date: 06 Nov 2009 17:59:05 GMT
On Wed, 04 Nov 2009 13:30:38 -0600, Moe Trin wrote:
On 04 Nov 2009, in the Usenet newsgroup alt.os.linux.redhat, in article
<4af1328d$0$31173$426a74cc@xxxxxxxxxxxx>, Steve wrote:
Moe Trin wrote:
What is causing the non-availability? Is the file server down, or not
accessible by existing networking? You may want to put a test to see
if the server is reachable before you try to mount from it.
I wrote a small script file, which try to access some servers. I know
that some of them, are not switched on all day long. So, the idea is to
start the script and connect to all servers available...
Normally, I'd consider testing to see if the server is up before
attempting to connect. Assuming the servers are configured to respond to
a ping (definitely not always the case), perhaps
ping -qc2 server_a
if [ $? = "0" ] ; then
connect_to_server_a
else
server_a_not_there
fi
ping -qc2 server_b
and so on. If the server is configured to not respond to pings (ICMP
Echo), then use something like hping2 or hping3 (http://www.hping.org/ -
but it doesn't seem to have been updated since 2005) to see if a UDP
port is reachable.
Old guy
Thank you. I will try it
thanks again for your help
.
- References:
- Mount point - timeout
- From: Steve
- Re: Mount point - timeout
- From: Moe Trin
- Re: Mount point - timeout
- From: Steve
- Re: Mount point - timeout
- From: Moe Trin
- Re: Mount point - timeout
- From: Steve
- Re: Mount point - timeout
- From: Moe Trin
- Mount point - timeout
- Prev by Date: Re: Changing UID and GID -> Some GUI problems.....
- Next by Date: sendmail won't use relay
- Previous by thread: Re: Mount point - timeout
- Next by thread: using a 32-bit library on a 64-bit machine
- Index(es):
Relevant Pages
|