topic Re: Socket problem in Operating System - HP-UX

Socket problem

Osa Jousou — Mon, 07 Jul 2003 14:48:51 GMT

We have a c program that opens and connects a socket to one of our vendors for the purpose of exchanging information. We disconnect the socket after midnight using ndd disconnect by address. The problem we're having is, when we start the process in the morning, the socket status starts in "Established" mode and since their are no files to exchange with the vendor the socket goes into "Time_Wait" status which causes our program to fail and socket to disconnect. My workaround, was to send a single packet at startup across the connection. That makes the socket stay open even if no data was exchanged for a couple of hours. I would like to know why it only works when I send that packet. If someone has a solution or suggestion to how I can get it to start without the initial packet, please send me your thoughts.

Re: Socket problem

A. Clay Stephenson — Mon, 07 Jul 2003 15:07:29 GMT

First of all using rather than using ndd to clobber the connections, I would rather see you code a signal handler to shutdown the socket more gracefully.

I suspect that you need to use setsockopt() to set SO_KEEPALIVE.

Re: Socket problem

Dagmar Boelen — Mon, 07 Jul 2003 15:12:31 GMT

You can configure you time-wait interval

ndd -get /dev/tcp tcp_time_wait_interval

-> this shows your current setting.

To change it
ndd -set /dev/tcp/tcp_time_wait_interval (in seconds)

to make it permanent
change the setting in
/etc/rc.config.d/nddconf

Re: Socket problem

Caesar_3 — Mon, 07 Jul 2003 19:41:15 GMT

Hello!

If it's your code i don't think that it's
a good thing that your program not control
the close of connection, you should check the
source and made changes and the work with
signals will be fine for this.

Caesar