09-18-2009
What are you looking for?
CLOSE_WAIT or FIN_WAIT issues?
9 More Discussions You Might Find Interesting
1. Programming
Hello,
I am having trouble clearing the serial port buffer using the iclear and iflush commands. The code runs without errors being returned, but when I check the buffer again there is still data.
The only way I have so far is to read until there is nothing left in the buffer. Shouldn't one... (1 Reply)
Discussion started by: sammy-e
1 Replies
2. Solaris
hi i have a sun machine which has one hba 2ports;
out of which one port says it is not connected
# luxadm -e port
/devices/pci@1d,700000/SUNW,qlc@1/fp@0,0:devctl CONNECTED
/devices/pci@1d,700000/SUNW,qlc@1,1/fp@0,0:devctl NOT CONNECTED
but both... (9 Replies)
Discussion started by: anwesh
9 Replies
3. Solaris
Hi Everyone,
In my environment, I have few T5220. On the iLOM Management Card, I have both Network and Serial port are cabled, I don't have any issues while I try to connect using Network Management port, but when I try to connect the serial port for the same server which is actually connected... (3 Replies)
Discussion started by: bobby320
3 Replies
4. IP Networking
Hi,
I am trying to set up a dev environment and I have Ubuntu server (10.16.1.92) and a CentOS VM (10.16.3.235) on this. On the CentOS I have a program running on port 5433. Now my problem is that I am unable to telnet this port from another Windows server whereas I can telnet port 22 from... (5 Replies)
Discussion started by: rishav
5 Replies
5. Solaris
:)Hi Solaris Experts,
I am wondering whether it is possible to clear a network socket port 17005 left by Apache Tomcat/6.0.20 after having to terminate it forcefully, since it has run away due to remote JDBC resource contention on another server. A normal Tomcat stop / shutdown proves... (2 Replies)
Discussion started by: gjackson123
2 Replies
6. IP Networking
i want to kill a tcp connection by killing its pid
with netstat -an i got the tcp ip connection on port 5914
but when i type ps -a or ps-e there is not such process running on port 5914
is it possible that because i do not log on with proper user account i can not see that process running? (30 Replies)
Discussion started by: alinamadchian
30 Replies
7. Solaris
Hello,
I have an unloaded T5140 machine and want to access the ILOM for the first time and subsequently the network port after that., and then load Solaris 10 the final January 2011 build.
The first part is what confuses me -the cabling.
I am coming from a Windows machine (w/appropriate... (5 Replies)
Discussion started by: joboy
5 Replies
8. 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
9. UNIX for Beginners Questions & Answers
hi,
i would like to create a bash script that check which port in my Linux server are closed (not in use) from a specific range, port range (3000-3010).
the print output need to be only 1 port, and it will be nice if the output will be saved as a variable or in same file.
my code is:
... (2 Replies)
Discussion started by: yossi
2 Replies
LEARN ABOUT DEBIAN
ieee1284_get_irq_fd
IEEE1284_GET_IRQ_FD(3) Functions IEEE1284_GET_IRQ_FD(3)
NAME
ieee1284_get_irq_fd, ieee1284_clear_irq - interrupt notification
SYNOPSIS
#include <ieee1284.h>
int ieee1284_get_irq_fd(struct parport *port);
int ieee1284_clear_irq(struct parport *port, unsigned int *count);
DESCRIPTION
If the port has a configured interrupt line and the port type supports interrupt notification, it is possible to obtain a file descriptor
that may be used for select(2) or poll(2). Any event (readable, writable or exception) means that an interrupt has been triggered. No
operations other than select or poll may be performed on the file descriptor.
The port must be open in order to call ieee1284_get_irq_fd, and must be claimed when using select or poll.
The caller must not close the file descriptor, and may not use it at all when the port is not claimed.
When an interrupt has been detected, the caller must call ieee1284_clear_irq to clear the interrupt condition, at which point the number of
interrupts raised can be obtained by supplying a non-NULL count.
RETURN VALUE
For ieee1284_get_irq_fd: If the return value is negative then it is an error code listed below. Otherwise it is a valid file descriptor.
E1284_NOTAVAIL
No such file descriptor is available.
E1284_INVALIDPORT
The port parameter is invalid (for instance, perhaps the port is not open).
For ieee1284_clear_irq:
E1284_OK
The interrupt has been cleared. If count was not NULL the count of interrupts has been atomically stored to count and reset.
E1284_NOTAVAIL
The count parameter was not NULL but interrupt counting is not supported on this type of port. The interrupt has been cleared.
E1284_SYS
There was a problem clearing the interrupt.
E1284_INVALIDPORT
The port parameter is invalid (for instance, perhaps the port is not claimed).
AUTHOR
Tim Waugh <twaugh@redhat.com>
Author.
COPYRIGHT
Copyright (C) 2001-2003 Tim Waugh
09/18/2007 IEEE1284_GET_IRQ_FD(3)