11-23-2006
Problem with name resolution?
I have an AIX4.3 box on our subnet, called LIMEST3.OURDOMAIN.CO.UK, with IP address 10.103.1.13
It has the following entry in its own /etc/hosts:
10.103.1.13 limest3 limest3.ourdomain.co.uk
Now, if I ping limest3.ourdomain.co.uk or ping 10.103.1.13, the result is instant. However if I ping limest3 it can take up to 30 seconds (I have verified that with 'time host').
No other AIX box on our subnet has this problem; pinging limest3 from another box is instant.
It may seem trivial, but I'm guessing it might have something to do with the sudden increase in time it takes to connect to our Oracle8i database (about 30 seconds).
A clue (perhaps): when we have lost internet access, the Oracle connection time shoots up to about 30s, and back down to near-instant when internet access is restored (the default gateway IS properly configured).
Any help would be very much appreciated.
10 More Discussions You Might Find Interesting
1. UNIX Desktop Questions & Answers
When i start my pc after the installation of suse linux it ask me for resolution but not for graphical interface, for console, can i run a command to change it again?
Thanx! (3 Replies)
Discussion started by: Linux_fan
3 Replies
2. UNIX for Advanced & Expert Users
My machine (Sun Blade 100) has just had it's OS reinstalled (solaris 8). For some reason the monitor resolution has changed (decreaded so that I have less monitor real esate).
Does anybody know the command to change monitor resolution in Solaris?
Cheers
AreaMan (2 Replies)
Discussion started by: AreaMan
2 Replies
3. Solaris
Hi,
I got solaris 10 installed on a E250 and i am expericing issues resolving dns.
from some research i think it's becuase where i haven't set-up NIS and i don't intend too as i am just setting up a box to poke communigate pro.
Any help or advice please?
Thanks in advance
Alan (1 Reply)
Discussion started by: e250user
1 Replies
4. Shell Programming and Scripting
We have the following code
filename=`head -1 $filelist`
if
then
touch $filename
fi
filelist contains the below items.
${HOME}/file1
${TEST_DIR}/file2
.
.
The output of the script described above is
${HOME} not found (3 Replies)
Discussion started by: krishmaths
3 Replies
5. Solaris
Hi,
I have a Sun Ultra 10 (SPARC) with Solaris 10 installed. The screen resolution is very poor and grainy which I have been unable to rectify. Every time I try to set the resolution I get the following:
'The XServer does not support the XRandR extension. Runtime resolution changes to the... (5 Replies)
Discussion started by: patcom
5 Replies
6. Debian
Hi gurus I have notebook with connected external monitor. output of my xrandr looks like
Screen 0: minimum 320 x 200, current 2960 x 1050, maximum 2960 x 1050
VGA connected 1680x1050+1280+0 (normal left inverted right x axis y axis) 478mm x 300mm
1680x1050 60.0*+
1280x1024 ... (2 Replies)
Discussion started by: wakatana
2 Replies
7. Solaris
Hi all!
On my SPARC mashine I have changed the screen resolution from default to: output-device screen r1024x768x75, because the OBP picture too big (e.g. Sun Logo and OBP text).
Now, after the system booting I have the problem with OpenWindows picture (e.g. the window manager does not display... (2 Replies)
Discussion started by: wolfgang
2 Replies
8. Red Hat
hi all
after going through ext3 file system , i understood that data resolution for ext3 FS is 1 second...can i increase it 2 second...? any idea..? (3 Replies)
Discussion started by: sagar_md
3 Replies
9. Debian
Hello,
I am running Debian 6.0 on a Sun Ultra 5 and the openbox window manager. The window is way larger than the screen and minimized icons go off the screen and I can't get them back. The mode is set to 1280x1024 in the Screen section of xorg.conf and Virtual is also set to 1280x1024 which is... (4 Replies)
Discussion started by: snorkack59
4 Replies
10. Red Hat
Good morning everyone,
I have been having screen resolution issues with RHEL 6.3. Our current setup is a laptop connected to a KVM/IP server. This is the desired scenario:
RHEL laptop
Windows XP laptop
KVM/IP server
The RHEL laptop has the file /etc/gdm/Init/Default populated with... (3 Replies)
Discussion started by: rchaud10
3 Replies
LEARN ABOUT DEBIAN
hobbitping
HOBBITPING(1) General Commands Manual HOBBITPING(1)
NAME
hobbitping - Xymon ping tool
SYNOPSIS
hobbitping [--retries=N] [--timeout=N] [IP-adresses]
DESCRIPTION
hobbitping(1) is used for ping testing of the hosts monitored by the xymon(7) monitoring system. It reads a list of IP adresses from stdin,
and performs a "ping" check to see if these hosts are alive. It is normally invoked by the bbtest-net(1) utility, which performs all of
the Xymon network tests.
Optionally, if a list of IP-adresses is passed as commandline arguments, it will ping those IP's instead of reading them from stdin.
hobbitping only handles IP-adresses, not hostnames.
hobbitping was inspired by the fping(1) tool, but has been written from scratch to implement a fast ping tester without much of the over-
head found in other such utilities. The output from hobbitping is similar to that of "fping -Ae".
hobbitping probes multiple systems in parallel, and the runtime is therefore mostly dependant on the timeout-setting and the number of
retries. With the default options, hobbitping takes approximately 18 seconds to ping all hosts (tested with an input set of 1500 IP
adresses).
SUID-ROOT INSTALLATION REQUIRED
hobbitping needs to be installed with suid-root privileges, since it requires a "raw socket" to send and receive ICMP Echo (ping) packets.
hobbitping is implemented such that it immediately drops the root privileges, and only regains them to perform two operations: Obtaining
the raw socket, and optionally binding it to a specific source address. These operations are performed as root, the rest of the time hob-
bitping runs with normal user privileges. Specifically, no user-supplied data or network data is used while running with root privileges.
Therefore it should be safe to provide hobbitping with the necessary suid-root privileges.
OPTIONS
--retries=N
Sets the number of retries for hosts that fail to respond to the initial ping, i.e. the number of ping probes sent in addition to
the initial probe. The default is --retries=2, to ping a host 3 times before concluding that it is not responding.
--timeout=N
Determines the timeout (in seconds) for ping probes. If a host does not respond within N seconds, it is regarded as unavailable,
unless it responds to one of the retries. The default is --timeout=5.
--responses=N
hobbitping normally stops pinging a host after receiving a single response, and uses that to determine the round-trip time. If the
first response takes longer to arrive - e.g. because of additional network overhead when first determining the route to the target
host - it may skew the round-trip-time reports. You can then use this option to require N responses, and hobbitping will calculate
the round-trip time as the average of all of responsetimes.
--max-pps=N
Maximum number of packets per second. This limits the number of ICMP packets hobbitping will send per second, by enforcing a brief
delay after each packet is sent. The default setting is to send a maximum of 50 packets per second. Note that increasing this may
cause flooding of the network, and since ICMP packets can be discarded by routers and other network equipment, this can cause
erratic behaviour with hosts recorded as not responding when they are in fact OK.
--source=ADDRESS
Use ADDRESS as the source IP address of the ping packets sent. On multi-homed systems, allows you to select the source IP of the
hosts going out, which might be necessary for ping to work.
--debug
Enable debug output. This prints out all packets sent and received.
SEE ALSO
xymon(7), bbtest-net(1), fping(1)
Xymon Version 4.2.3: 4 Feb 2009 HOBBITPING(1)