04-24-2009
This generally is an application issue (look at SO_LINGER for example). The client is not receiving the CLOSE_WAIT confirmation from the server and thus leaving the socket open or visa versa. May also (rarely) be caused by settings in network routers and switches which limit packet size. Do a Web search - lots of information on this issue out there on the Internet.
You should be able to use sysctl to manage this issue until you figure out which application is causing the problem.
9 More Discussions You Might Find Interesting
1. UNIX for Advanced & Expert Users
Hi
Should anyone be able to help, one of my colleagues was doing a truss this morning and I am not sure if it has offset the system crash, but we have had these type of errors coming up????
# ls
ls: Cannot read /usr/lib/ld.so.1
Killed
# ps -ef
ps: Cannot read /usr/lib/ld.so.1
Killed
#... (1 Reply)
Discussion started by: NAV4869
1 Replies
2. Solaris
Hi,
I have a Sun 3500 server on which i installed solaris 8 and have also installed veritas 4.0 on it. i dont know why from the time i have built this server whenever i try to boot it, the server doesnot come back smooth.... i have got to connect a laptop to the serial port of the server and... (3 Replies)
Discussion started by: ishila
3 Replies
3. UNIX for Dummies Questions & Answers
how do i mointor how many sockets are opened from a particular foriegn address? (2 Replies)
Discussion started by: kirpond
2 Replies
4. Solaris
Is there a way to see what sockets are in use? The developers here are getting some defunct processes and they would like to get a socket list.
This is on a Solaris 8 machine.
Thanks! (1 Reply)
Discussion started by: kjbaumann
1 Replies
5. Solaris
Hellocan someone tell me if there are any special tricks at hand t set up Solaris 10 on a Enterprise 3500? I`ve tried with different cd`s, burnt on different speeds, and also with bought one`s. All give the same result after boot cdrom, it starts but freezes right after the license message.And... (16 Replies)
Discussion started by: vatch23
16 Replies
6. Solaris
Hi,
I have two Sun Fire V490 with Solaris 10 5/08, FC switch and two Sun StorageTek 3500 FC arrays. Each array is connected to switch and to one server at a time. In the last week I installed Solaris 10 5/08 on both servers and set up Sun Cluster, version 3.2. At wednesday all was fine - all... (7 Replies)
Discussion started by: Sapfeer
7 Replies
7. Programming
Hi,i now moved into a different section where i need to use sockets.
i am completely nill in sockets.
can some body please provide me what are the requirements for a socket.
to use sockets in c.
thanks (1 Reply)
Discussion started by: MrUser
1 Replies
8. Programming
if i have a server which wants to connect to exactly 5 clients, does that mean i need 5 socket file descriptors and use
listen(socket_fd,1);
for each one
or just do
listen(socket_fd,5)
also whats the second parameter number mean? what happens if i put 0 there?
also if i am connected... (28 Replies)
Discussion started by: omega666
28 Replies
9. Solaris
Booting problem on Sun 3500
Hi,
I have a Sun 3500 server on which i installed solaris 5.2 installed . i dont know why from the time i have built this server whenever i try to boot it, the server doesnot come back smooth.i got a message Sync file system than restart
some times showing ok... (2 Replies)
Discussion started by: najeer
2 Replies
LEARN ABOUT DEBIAN
obex_test
OBEX_TEST(1) User commands OBEX_TEST(1)
NAME
obex_test - interactive test application for the openobex library
SYNOPSIS
obex_test [[-s port] | [-r port] | [-i] | [-b [address] [channel]] | [-u interface]]
DESCRIPTION
obex_test is a test application for the openobex library. It uses an interactive mode but the access method is selcted with command line
arguments.
This program is designed to be an example application for the openobex library.
OPTIONS
-s
This is the default. It selects cable obex. The port argument is optional (default: /dev/ttyS0)
-r
Select cable obex for the Ericsson R320 mobile phone. The port argument is optional (default: /dev/ttyS0)
-i
Select obex over IrDA.
-b
Select obex over bluetooth. Both, address and channel are actually optional. Default channel is 4, default address is ANY.
-u
Select usb obex (CDC). If the interface argument is omitted, a list of available interface is written to stdout.
INTERACTIVE MODE
: COMMANDS
c
connect to the remote side (client mode)
d
disconnect from the remote side
g
issue a GET request
p
issue a PUT request
q
quit the program
s
go into server mode
t
change the path on the remote side
x
issue a PUSH request
AUTHOR
Hendrik Sattler <post@hendrik-sattler.de>
initial version of manpage
openobex 1.4 2008-11-23 OBEX_TEST(1)