socket close() -w- pthreads linux 2.6.18.2-34 (suse) SMP Post: 302164955

7 More Discussions You Might Find Interesting

1. Programming

C Prog to close a socket in established state

I have a SUN environment running an WebLogic that communicates w/a 3rd party running IIS. When the IIS site goes down (frequently), I am stuck with sockets in an ESTABLISHED state, and cannot seem to figure out how to avoid this. No exceptions are thrown as I can still open connections to the IIS...

2. UNIX for Dummies Questions & Answers

SMP support in Linux 7.3

What is the SMP support like when you are running Linux 7.3 on a system with 2-4 CPUs?

3. Linux Benchmarks

Dual Intel Xeon 2.4Ghz - Linux 2.4.26 SMP

System: CPU/Speed: Dual Intel Xeon 2.4Ghz Ram: 2 GB DDR 266 SDRAM Motherboard: SuperMicro X5DE8-GG Bus: 533MHz/400MHz system bus - Cache: 512KB HD Controller: EIDE Serverworks� GC-SL Chipset Extra GCC compiler flags: -s...

4. HP-UX

socket close hangs and CPU go to 100%

Hello, I'm currently having a problem with HPUX. The application is a C app. It's a socket server. It runs mostly fine, but under some circumstances (I can not replicate it), the app hangs and the CPU goes to 100%. I have use gdb to attach to the app, and it was doing a close(). the...

5. HP-UX

Close Socket at HP-UX

Hi all, I have a HP-UX 11.23 that have a Server establishing connections on port 8888 . The problem is that when i need to stop and restart the Server, the connections mantain the same state and i need to wait about 20-30 minutes before all connections finishes. The connections remain at...

6. UNIX and Linux Applications

any way to close socket

I have written a socker program. I have executed that program many times without closing the socket. So I want to find which all sockets binded with which file descriptor. Is there any way to close those socket, which have been opened in that program's execution. please help me!..

7. IP Networking

Is it necessary to close socket after a unstop loop?

Is the last two line necessary? #include <sys/types.h> #include <sys/socket.h> #include <netinet/in.h> #include <arpa/inet.h> #include <stdio.h> #include <stdlib.h> #include <string.h> #include <unistd.h> int main(void) { struct sockaddr_in stSockAddr; ...

LEARN ABOUT CENTOS

pcic

PCIC(4) 						   BSD Kernel Interfaces Manual 						   PCIC(4)

NAME

     pcic -- PC Card bridge driver

SYNOPSIS

     device pcic
     device pccard

DESCRIPTION

     The pcic driver provides support for older ISA and non-Yenta PCI PC Card bridges.	The pcic driver supports most ExCA devices attached to the
     ISA bus or PCI devices that do not conform to the Yenta specification.

     The following ISA devices, or true clones, are supported in the current code.

     Intel i82365SL Step A
     Intel i82365SL Step B
     Intel i82365SL Step C  Intel's original 16-bit PC Card controller.
     Intel i82365SL-DF	    Intel's last version of this device.  3.3V support was added.
     VLSI 82C146	    An older VLSI part with some issues on some machines.
     Cirrus Logic PD-6710
     Cirrus Logic PD-6720
     Cirrus Logic PD-6722   Cirrus Logic's pcic controller.  Compatible with the i82365SL Step C with the addition of a different 3.3V control.
     Ricoh RF5C296
     Ricoh RF5C396	    Ricoh's PC Card bridge chips.  These are compatible with the i82365SL Step C, but with yet another different 3.3V con-
			    trol.
     Vadem 365
     Vadem 465		    Compatible with i82365SL Step C.
     Vadem 468
     Vadem 469		    Like the earlier Vadem models, but with Vadem's own, incompatible, 3.3V control system.
     IBM PCIC		    IBM clone of the original i82365SL part, with its own ID register value.  Has no 3.3V ability.

     Many other vendors made parts in this arena, but most of them were compatible with one of the above chipsets.

     The following PCI pcmcia bridges are supported:

     Cirrus Logic PD6729
     Cirrus Logic PD6730

     O2micro OZ6729
     O2micro OZ6730

BUGS

     This does not work at all at the moment.

BSD
								   July 9, 2002 							       BSD