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

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

On Tue, Apr 16, 2002 at 02:40:44PM +0200, Lhota Robert wrote:
> > Hello,
> > 
> > I am using dnping (Linux-DECNET) for testing the availability of VAX
> > machines. The timeout is set for 3 seconds. Unfortunately, dnping
> > program does not implement timeout feature, so I have to kill the
> > child-process if it does not respond in the timeout period. The side
> > effect of this is that the DECNET stack on Linux does not close the
> > connection to the VAX machine. The number of connections (users) on
> > VAX machines is increasing and cosuming resources. Does anybody know
> > how to clear these connections on the Linux side? Can I just restart
> > the decnet stack (/etc/init.d/decnet restart) or is there some other
> > way? It looks like to me that the decnet stack somehow remembers the
> > connections even after service is restarted.

You're right. It's not just dnping but any DECnet connections. They don't seem
to close when the application is aborted using ^C

$ cat /proc/net/decnet
Local                                              Remote
  1.10/201A 0001:0013 0000:0001 2 LINUX              1.30/201B 0000:0001 0000:0012 2 25                RUN IMMED
  1.10/201B 0001:0013 0000:0001 2 LINUX              1.30/201C 0000:0001 0000:0012 2 25                RUN IMMED
  1.10/201C 0001:0013 0000:0001 2 LINUX              1.30/201D 0000:0001 0000:0012 2 25                RUN IMMED
  1.10/201D 0001:0013 0000:0001 2 LINUX              1.30/201E 0000:0001 0000:0012 2 25                RUN IMMED
  1.10/201E 0001:0006 0000:0001 2 PATRICK            1.30/201F 0000:0001 0000:0005 2 17                RUN IMMED
  1.10/201F 0001:0005 0000:0001 2 PATRICK            1.30/2020 0000:0001 0000:0004 2 17                RUN IMMED
  1.10/2020 0001:0005 0000:0001 2 PATRICK            1.30/2021 0000:0001 0000:0004 2 17                RUN IMMED
  1.10/2021 0001:0005 0000:0001 2 PATRICK            1.30/2023 0000:0001 0000:0004 2 17                RUN IMMED
  1.10/2022 0001:0005 0000:0001 2 PATRICK            1.30/2024 0000:0001 0000:0004 2 17                RUN IMMED

$ mc ncp sho kno links
 
 
Known Link Volatile Summary as of 16-APR-2002 14:06:56
 
   Link       Node           PID     Process     Remote link  Remote user
 
  8219    1.10 (ARTHUR)    000000BC  MIRROR_8219        8218  LINUX
  8220    1.10 (ARTHUR)    000000BD  MIRROR_8220        8219  LINUX
  8221    1.10 (ARTHUR)    000000BE  MIRROR_8221        8220  LINUX
  8222    1.10 (ARTHUR)    000000BF  MIRROR_8222        8221  LINUX
  8223    1.10 (ARTHUR)    000000C1  FAL_8223           8222  PATRICK
  8224    1.10 (ARTHUR)    000000C2  FAL_8224           8223  PATRICK
  8225    1.10 (ARTHUR)    000000C3  FAL_8225           8224  PATRICK
  8227    1.10 (ARTHUR)    000000C4  FAL_8227           8225  PATRICK
  8228    1.10 (ARTHUR)    000000C5  FAL_8228           8226  PATRICK
  8231    1.10 (ARTHUR)    00000102  FAL_8231           8229  PATRICK

As a temporary workaround you can remove the connections using the 
NCP DISCONECT LINK 
command but it looks quite nasty.


Steve?

patrick