Re: Question

In article <35F842AB.41E3@bloomberg.net>, kagel@bloomberg.net (Art S. Kagel) wrote: > Jair Huerta wrote: > > > > Dear all: > > I want to know if is possible to take down TCP when you want > > to > > kill the sqlexec daemon, I mean if i want to kill the daemon and then > > put it to work again, is not possible > > because the bind address is already in use, because there are > > That bind address already in use is because the OS's TCP drivers have > not timed out the connections yet. There is a tunable or something to > tell the driver to not keep old connections alive (keepalive or some > such). Talk to your sysadmin or HP Tech support. This is a problem > with many UNIX's. > > Art S. Kagel > Your network connection has moved to a FIN_WAIT state 'cos the tcp sub-system has detected the connection has died, but it session has not released the resources correctly. AFAIK this is because the 'wrong' call is made in the closure - you'll need to ask in tcp newsgroup to get a full explanation. Where most of the tcp parameters are tuneable I do not believe the FINWAIT(s) timeout can be altered - if it can please tell me. As an aside stopping an engine with users connected using onmode -ky can leave connections but using onmonitor and immediate shutdown doesn't - Why? Paul Watson # I don't suffer from WF Software Ltd. # stress, I'm just Tel. (+44) 1436 674729 # a carrier Fax. (+44) 1436 678693 #