Re: [Linux-decnet-user] Closing DECNET connections

[Patrick C. <pa...@ty...>]

On Tue, Apr 16, 2002 at 02:06:00PM +0100, Steven Whitehouse wrote:
> Hi,
> 
> [snip]
> > 
> > 
> > Steve?
> > 
> > patrick
> > 
> > 
> Hmm. Not sure about that. When the socket gets closed (along with all the
> other fds of that process it should get shutdown. The release function has
> the code in it to force that. Are you sure that there isn't something keeping
> the socket open somehow ?
> 
> I don't know why a signal should cause this because the destruction of a
> socket should be the same code path whatever caused the process to exit.
> I wonder if you add a signal handler to the application which does:
> 
> 	close(socket);
> 	exit(0);
> 
> whether you still get the same problem ? What kernel version are you using ?
> 
> I know some of the DECnet code can be a bit slow in places in shutting down
> sockets as its overcautious, but I've not seen hangs in the RUN state
> before,

I've never seen it before but now it seems consistent, if I ^C a process with an
open connection it stays in RUN. I'm running kernel 2.4.17 

Oddly adding the signal handler makes no difference - the sockets still stick in
RUN (yes, I put a prinf in the signal handler so I knew it was being called!)

But they go away if I let the program run to completion.

Wierd.

patrick


P.S. Just noticed this too - I think It'd be nice if the link numbers in
/proc/net/decnet was in decimal rather than hex then it is possible to match
them up with those shown by VMS.