Exceeded User Count

[Kenneth Brody]

Quoting charles day <daychls at verizon.net>:

> Kenneth Brody wrote:
[...]
> >the problems.  It's not "the delete key", but rather "clicking the 'x'
> > in
> >the upper-right corner on an MS-Windows box that's connected to the
> *nix
> >box" that's the problem.  If you close the window without exiting, then
> >the O/S may not see the disconnect, and filePro (as well as any other
> >application) will continue running in that session.
>
> Prior to XP when one clicked  X  to close the window,  Windows would
> tell you it can't do that.
> On XP the window will close without telling you it can't.

We're talking about a telnet session to a *nix box, not a command
window on the Windows box.

> Does this mean on a Windows network that filPro is not really being
> closed ?

Closing the command window on Windows causes filePro to exit as well.
However, I am not sure if it's a clean exit or not.  (An easy check
would be to be in update on a record in *clerk and close the window.
Then, see if the lockfile says someone is still in the file [try going
into ddefine], and see if the record lock was released by trying to
update it in a new *clerk.)

> Or, is it only when hooked to Unix it does not close?

Some systems don't seem to send or receive the proper socket shutdown
commands when you exit with the "x" to close the window.  This causes
the *nix box to keep the session open, and as such the filePro program
is still running.

--
KenBrody at BestWeb dot net        spamtrap: <g8ymh8uf001 at sneakemail.com>
http://www.hvcomputer.com
http://www.fileProPlus.com