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

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

On Wed, Apr 17, 2002 at 04:27:49PM +0200, Lhota Robert wrote:
> Thank you very much for the timeout option. I think it solves my
> problem. I had to comment out the section:
> 
> if (options & DNF_TIMEOUT)
> 	{
> 	    int status;
> 	    fd_set in_fd;
> 
> 	    FD_ZERO(&in_fd); 
> ...
> 
> because it caused the program exit with "Timeout" every time when used
> with options -t -w together (f.e. dnping -t -w 10 11.42). Instead of
> that I extended the alarm to the all program by commenting out alarm(0)
> function. I am not c-coder at all but this works for me now.

Aha typo! here's the fix:
diff -u -r1.4 dnping.c

--- dnping.c    17 Apr 2002 07:42:31 -0000      1.4
+++ dnping.c    17 Apr 2002 14:41:19 -0000
@@ -423,7 +423,7 @@
            timeout.tv_sec = timeout_sec;
            timeout.tv_usec = 0;
 
-           status = select(sockfd+1, &in_fd, NULL, NULL, &tv);
+           status = select(sockfd+1, &in_fd, NULL, NULL, &timeout);
            if (status < 0)
            {
                perror("select");


 
> Do I understand it right, that
> mc ncp sho kno links
> and
> NCP DISCONECT LINK 
> are VAX machine commands and cannot be used on Linux implementation of
> DECNET? Is there than any possibility how to clear the "zombie
> connections" from Linux? I tried to restart decnet vie startup scripts
> (/etc/init.d/decnet on RedHat) but it didn't clear the connections and
> even than  I could not dnping the hosts that were in the connections any
> more (after decnet restart).

Yes, those are VMS commands, there is no Linux equivalent that I know of - and
you need privileges on VMS to do it.

If you do that command on VMS then the Linux connections will timeout.

patrick