03-02-2013
What could have happened is that IP connections have a (too) long time-out value. Depending on the OS you are using (Linux? HP-Ux? AIX? NetBSD? Solaris? ...?) there are different methods to change this and tune the IP stack. In AIX (but only there, so this won't help you if it is not AIX) it would be some tunables accessible by "no".
When you tell us the OS you are using: please also tell the exact version! AIX, for instance, changed a lot of its kernel tuning from 5.3 to 6.x and from 6.x to 7.x again.
In any case, you will definitely need root-privileges to change these values, so you definitely should get one of the SysAdmins to work. Don't be shy, this is their job.
I hope this helps.
bakunin
10 More Discussions You Might Find Interesting
1. IP Networking
I am trying to connect via DBACCESS and Informix server to a server on a different computer. When I execute the connect command from dbaccess I get the following message,
Exec format error cannot bind a name to the port.
As far as I know the port is not being used by another client.
How... (1 Reply)
Discussion started by: lopez
1 Replies
2. UNIX for Dummies Questions & Answers
Hi All, I suspect this is simple but I cannot find any info on it.
I have a logfile on a solaris box (EMS) that I want to tail -f but I want the output of this to be redirected to a TCP port.
I have a second solaris box (PEM) running patrol enterprise manager that I am using as an alarm... (1 Reply)
Discussion started by: mscomms
1 Replies
3. UNIX for Dummies Questions & Answers
Hi
Is there any way to restrict the TCP-IP port usage.
I want to restrict TCP-IP port 1500/1550 to the oracle osuser.
Tanks in advance.
Remi (2 Replies)
Discussion started by: remivisser
2 Replies
4. Solaris
Hi all
I haven't had much experience with Solaris 10 but we've started running into a problem where a process hangs, it is killed and leaves a zombie process. The sysadmins are saying this zombie process is locking a tcp port and not allowing the process to start up.
The process is a usually... (5 Replies)
Discussion started by: casphar
5 Replies
5. UNIX for Dummies Questions & Answers
Hello, I have a service running (ODBC) and every now and then it will hang and I will have to stop and restart the service. The problem is when I stop the service, it indeed stops the service, but netstat reports a tcp port still open with the fin_wait_2 status. Then I must close the client... (1 Reply)
Discussion started by: raidzero
1 Replies
6. IP Networking
Hi. I ran nmap on my server, and I get the following:
Starting Nmap 4.76 ( http://nmap.org ) at 2009-03-19 16:33 EDT
Interesting ports on -------- (-----):
Not shown: 997 closed ports
PORT STATE SERVICE
22/tcp open ssh
80/tcp open http
6881/tcp open bittorrent-tracker
The... (0 Replies)
Discussion started by: Rledley
0 Replies
7. Shell Programming and Scripting
I have multiple processes running the same program on my linux machine. For each process I want to be able to use a unique (available) TCP port. I have thought of using netstat to check which ports are available for use however, the time-window between checking and selecting might expose some race... (1 Reply)
Discussion started by: timmylita
1 Replies
8. UNIX for Advanced & Expert Users
Hey guys,
I need to kill the process that is currently connected to port 10540. I'm on HP-UX machine.
Below is the result of my netstat.
$ netstat -an |grep 10540
tcp 0 0 129.0.0.1.10540 *.* LISTEN
We don't have lsof command, but we have fuser.
... (3 Replies)
Discussion started by: brichigo
3 Replies
9. Programming
Hello,
I'm trying to write a small c application to test a tcp port. This works fine for the most part but the default timeout on the connect is very long. I have been reading many posts but and it looks like I need to set the socket to be non-blocking and poll for a result. I have been totally... (2 Replies)
Discussion started by: tjones1105
2 Replies
10. Solaris
please find the below o/p for your reference
bash-3.00# fcinfo hba-port
HBA Port WWN: 21000024ff295a34
OS Device Name: /dev/cfg/c2
Manufacturer: QLogic Corp.
Model: 375-3356-02
Firmware Version: 05.03.02
FCode/BIOS Version: BIOS: 2.02; fcode: 2.01;... (3 Replies)
Discussion started by: sb200
3 Replies
pcilib(7) The PCI Utilities pcilib(7)
NAME
pcilib - a library for accessing PCI devices
DESCRIPTION
The PCI library (also known as pcilib and libpci) is a portable library for accessing PCI devices and their configuration space.
ACCESS METHODS
The library supports a variety of methods to access the configuration space on different operating systems. By default, the first matching
method in this list is used, but you can specify override the decision (see the -A switch of lspci).
linux-sysfs
The /sys filesystem on Linux 2.6 and newer. The standard header of the config space is available to all users, the rest only to
root. Supports extended configuration space, PCI domains, VPD (from Linux 2.6.26), physical slots (also since Linux 2.6.26) and
information on attached kernel drivers.
linux-proc
The /proc/bus/pci interface supported by Linux 2.1 and newer. The standard header of the config space is available to all users, the
rest only to root.
intel-conf1
Direct hardware access via Intel configuration mechanism 1. Available on i386 and compatibles on Linux, Solaris/x86, GNU Hurd and
Windows. Requires root privileges.
intel-conf2
Direct hardware access via Intel configuration mechanism 2. Available on i386 and compatibles on Linux, Solaris/x86, GNU Hurd and
Windows. Requires root privileges. Warning: This method is able to address only the first 16 devices on any bus and it seems to be
very unreliable in many cases.
fbsd-device
The /dev/pci device on FreeBSD. Requires root privileges.
aix-device
Access method used on AIX. Requires root privileges.
nbsd-libpci
The /dev/pci0 device on NetBSD accessed using the local libpci library.
obsd-device
The /dev/pci device on OpenBSD. Requires root privileges.
dump Read the contents of configuration registers from a file specified in the dump.name parameter. The format corresponds to the output
of lspci -x.
PARAMETERS
The library is controlled by several parameters. They should have sensible default values, but in case you want to do something unusual (or
even something weird), you can override them (see the -O switch of lspci).
Parameters of specific access methods
dump.name
Name of the bus dump file to read from.
fbsd.path
Path to the FreeBSD PCI device.
nbsd.path
Path to the NetBSD PCI device.
obsd.path
Path to the OpenBSD PCI device.
proc.path
Path to the procfs bus tree.
sysfs.path
Path to the sysfs device tree.
Parameters for resolving of ID's via DNS
net.domain
DNS domain containing the ID database.
net.cache_name
Name of the file used for caching of resolved ID's.
SEE ALSO
lspci(8), setpci(8), update-pciids(8)
AUTHOR
The PCI Utilities are maintained by Martin Mares <mj@ucw.cz>.
pciutils-3.1.7 31 January 2010 pcilib(7)