RE: RE: RE: Thin Clients and TCP/IP

[Chris Bipes <chris.bipes@xxxxxxxxxxxxxxx>]

We have a very, very old piece of software that controls session inactivity
by user profile.  Basically you set your system value to send a message to a
message queue where a program sits waiting for incoming messages.  It parses
the messages to get the user name etc. and looks up the user in the file.
If the user exist, it follows the instruction on file.  If not, it uses
default values.  I was a purchase package back on an old B40 under 1.2 and
STILL WORKS on our 720 @ 4.4

Christopher K. Bipes      mailto:ChrisB@Cross-Check.com
Operations & Network Mgr  mailto:Chris_Bipes@Yahoo.com
CrossCheck, Inc.                  http://www.cross-check.com
6119 State Farm Drive     Phone: 707 586-0551 x 1102
Rohnert Park CA  94928    Fax: 707 586-1884

-----Original Message-----
From: Mike Naughton [mailto:mnaughton@juddwire.com]
Sent: Thursday, May 10, 2001 6:29 AM
To: MIDRANGE-L@midrange.com
Subject: Re: RE: RE: Thin Clients and TCP/IP


Hi Dale,

I got a little more info today -- apparently, we've got very big time-out
values on our system because the operators in the shop (the same ones
getting the thin clients) really do use their machines very sporadically
as a general rule.  They'll log a few values into the system, then run the
machine for a while (maybe hours), then log a few more values, etc. So
time-outs aren't going to help us, and I'm not sure there's anything that
will. . . . 

At least it's not the worst problem we could have -- really an annoyance,
more than anything. Anyway, thanks again for your help!

MIDRANGE-L@midrange.com writes:
>The extra unused sessions only hang around for a little bit before timing
>out. Try it sometime and time how long it takes from another session. I'm
>pretty darn sure a named device can only have one session, but, one client
>*could* have more than one named device. It would just be another shortcut
>on the desktop. But, if you are choking down your user to use only a named
>device, well, fugettaboutit, your security is going to force this problem
>and nothing you can do about it except to train the user to wait X minutes
>before trying to sign on again. See sentence #2 above.


Mike Naughton
Senior Programmer/Analyst
Judd Wire, Inc.
124 Turnpike Road
Turners Falls, MA  01376
413-863-4357 x444
mnaughton@juddwire.com

+---
| This is the Midrange System Mailing List!
| To submit a new message, send your mail to MIDRANGE-L@midrange.com.
| To subscribe to this list send email to MIDRANGE-L-SUB@midrange.com.
| To unsubscribe from this list send email to MIDRANGE-L-UNSUB@midrange.com.
| Questions should be directed to the list owner/operator:
david@midrange.com
+---
+---
| This is the Midrange System Mailing List!
| To submit a new message, send your mail to MIDRANGE-L@midrange.com.
| To subscribe to this list send email to MIDRANGE-L-SUB@midrange.com.
| To unsubscribe from this list send email to MIDRANGE-L-UNSUB@midrange.com.
| Questions should be directed to the list owner/operator: david@midrange.com
+---