Path: utzoo!utgpu!jarvis.csri.toronto.edu!cs.utexas.edu!samsung!brutus.cs.uiuc.edu!lll-winken!attdso!westmark!dave
From: dave@westmark.UU.NET (Dave Levenson)
Newsgroups: comp.dcom.lans
Subject: Re: What does "link" mean in a 3Com LAN?
Message-ID: <400@westmark.UU.NET>
Date: 2 Feb 90 00:43:13 GMT
References: <213.25c4249b@acci.com>
Organization: Westmark, Inc., Warren, NJ, USA
Lines: 25

In article <213.25c4249b@acci.com>, ta2@acci.com writes:
...
> I have been told that the application program does not "unlink" at
> program exit. What does this mean?

I'll take a stab at your question, but first, let me say that I'm
assuming something about the context in which it was asked:  I'm
assuming that your application is running on a MS-DOS machine that
is a client, and that the application creates a link to a shared
resource (a shared directory or printer) on a server.  Link is the
operation that re-directs a device (such as D: or E: or LPT1:) to a
shared resource.  Unlink breaks the association -- i.e. it
disassociates the local device name from the shared resource.

In many lan installations, links are created when the client is
booted, and remain up until the client is shut down.  But if you
have an application that performs its own link, then for
completeness (finish what you started...) it probably ought to
unlink before it exits.

-- 
Dave Levenson			Voice: (201 | 908) 647 0900
Westmark, Inc.			Internet: dave@westmark.uu.net
Warren, NJ, USA			UUCP: {uunet | rutgers | att}!westmark!dave
[The Man in the Mooney]		AT&T Mail: !westmark!dave