Hello...the unix server that runs our hotels check-in software (aix
ibm) keeps running out of licenses during the day..we have plenty of
licenses for the software (170 licenses and 60 users) but users end up
opening up multiple terminal sessions so licenses run low and or run
out during the day sometimes which causes problems...all front desk
sessions log in as "guest" so all sessions pts/** have same session
name "guest"...we where wondering if there was a reasonable automated
way to have idle sessions (just the "guest" sessions) get disconnected
after an hour (or some other time frame) of idle time?.This way we
don't have to go in and kill sessions so much.We are not aix/unix gods
so if you guys could explain to relative neophytes..that would be very
cool indeed…thanks in advance from the maine woods

[ Post a follow-up to this message ]

On 17 Mar 2004 12:50:48 -0800, maine666@hotmail.com (david) wrote:

>Hello...the unix server that runs our hotels check-in software (aix
>ibm) keeps running out of licenses during the day..we have plenty of
>licenses for the software (170 licenses and 60 users) but users end up
>opening up multiple terminal sessions so licenses run low and or run
>out during the day sometimes which causes problems...all front desk
>sessions log in as "guest" so all sessions pts/** have same session
>name "guest"...we where wondering if there was a reasonable automated
>way to have idle sessions (just the "guest" sessions) get disconnected
>after an hour (or some other time frame) of idle time?.This way we
>don't have to go in and kill sessions so much.We are not aix/unix gods
>so if you guys could explain to relative neophytes..that would be very
>cool indeed…thanks in advance from the maine woods

I'm not aware of anything 'built-in' to AIX that does what you are
after, and I'm not seeing anything in the man pages (quick look).
SCO Openserver has 'idleout', but that doesn't help you (and I don't
know that it will perform based on UID).

There is the logmon package (http://www.logmon.com/) - Not cheap, but
it may be in the ballpark depending on how much of your (and your
user's) time is involved trying to police your current scenario.


Scott McMillan

[ Post a follow-up to this message ]

Scott McMillan <smcm@usa.net> wrote in message news:<chhh5011ouft941ckvadtinenehv9bct27@4ax
.com>...
> On 17 Mar 2004 12:50:48 -0800, maine666@hotmail.com (david) wrote:
> 
>
> I'm not aware of anything 'built-in' to AIX that does what you are
> after, and I'm not seeing anything in the man pages (quick look).
> SCO Openserver has 'idleout', but that doesn't help you (and I don't
> know that it will perform based on UID).
>
> There is the logmon package (http://www.logmon.com/) - Not cheap, but
> it may be in the ballpark depending on how much of your (and your
> user's) time is involved trying to police your current scenario.

Scott thanks for answering and doing some research on the subject...I
dont think we will get any money to buy software to fix problem..even
though that would make sense..is there a script  or modification to
aix that we could add...maybe not going the idle user route but maybe
limiting each pc to one  terminal session...this might be difficult
because each front desk terminal has same login...any ideas
guys?...thanks in advance...David
>
>
> Scott McMillan

[ Post a follow-up to this message ]

"david" <maine666@hotmail.com> wrote in message
news:41095901.0403180448.3db2c6c4@posting.google.com...
> Scott McMillan <smcm@usa.net> wrote in message
news:<chhh5011ouft941ckvadtinenehv9bct27@4ax.com>... 
>
> Scott thanks for answering and doing some research on the subject...I
> dont think we will get any money to buy software to fix problem..even
> though that would make sense..is there a script  or modification to
> aix that we could add...maybe not going the idle user route but maybe
> limiting each pc to one  terminal session...this might be difficult
> because each front desk terminal has same login...any ideas
> guys?...thanks in advance...David 

Could you check for a duplicate IP address.  You could use "who am i" to get
the IP of the PC that is trying to log in and then check to see if that IP
is already logged in using who.

John Hill

[ Post a follow-up to this message ]

david wrote:
>
> the unix server that runs our hotels check-in software (aix
> ibm) keeps running out of licenses during the day..we have plenty of
> licenses for the software (170 licenses and 60 users) but users end up
> opening up multiple terminal sessions so licenses run low

Then what you have is a user training issue.  Use the right tool for
the job.  Killing idle sessions is solving the wrong problem.  Much
of engineering is figuring out what the right thing to do is.

[ Post a follow-up to this message ]

On 18 Mar 2004 08:30:02 -0800, Doug Freyburger <dfreybur@yahoo.com> wrote:
>
> Then what you have is a user training issue.  Use the right tool for
> the job.  Killing idle sessions is solving the wrong problem.  Much
> of engineering is figuring out what the right thing to do is.

Agreed.  One solution would be to train them not to do that.  One way
to train them not to do that, is to not allow them to do that - open a
session, it looks to see if they have other sessions open on that box and
if so, says "Failed to initiate session - duplicate license attempt" or
something equally attention-getting.

There are probably dozens of other ways to handle it, but a simple "Is
this person already running this tool on this workstation" would get you
much of the way there.  A license manager timeout (release license if
idle for x minutes) might be useful here too, depending on more things
than we know about what you're doing.

Dave Hinz

[ Post a follow-up to this message ]

david wrote:
> Hello...the unix server that runs our hotels check-in software (aix
> ibm) keeps running out of licenses during the day..we have plenty of
> licenses for the software (170 licenses and 60 users) but users end up
> opening up multiple terminal sessions so licenses run low and or run
> out during the day sometimes which causes problems...all front desk
> sessions log in as "guest" so all sessions pts/** have same session
> name "guest"...we where wondering if there was a reasonable automated
> way to have idle sessions (just the "guest" sessions) get disconnected
> after an hour (or some other time frame) of idle time?.This way we
> don't have to go in and kill sessions so much.We are not aix/unix gods
> so if you guys could explain to relative neophytes..that would be very
> cool indeed…thanks in advance from the maine woods

Why not amend the login scripts thusly

if (already a session on this tty)
echo You are already logged in. Max one session per terminal.
sleep 3
exit
end if

(assuming they have the pseudo-code shell as their login shell :-)

I'd dress it up by creating a lock file (probably in /tmp) and catching
interrupts to ensure it is deleted at end of session.

YMMV, Batteries not included.

[ Post a follow-up to this message ]

On 17 Mar 2004 12:50:48 -0800, maine666@hotmail.com (david) wrote:

>Hello...the unix server that runs our hotels check-in software (aix
>ibm) keeps running out of licenses during the day..we have plenty of
>licenses for the software (170 licenses and 60 users) but users end up
>opening up multiple terminal sessions so licenses run low and or run
>out during the day sometimes which causes problems...all front desk
>sessions log in as "guest" so all sessions pts/** have same session
>name "guest"...we where wondering if there was a reasonable automated
>way to have idle sessions (just the "guest" sessions) get disconnected
>after an hour (or some other time frame) of idle time?.This way we
>don't have to go in and kill sessions so much.We are not aix/unix gods
>so if you guys could explain to relative neophytes..that would be very
>cool indeed…thanks in advance from the maine woods


What version of AIX are you running?  As far as I can remember, recent
versions of AIX have come with unlimited licenses.  There is a setting
however that you need to raise to allow more users.

Is it definately a license issue? what messages are you getting?  It
could be that you are not allowing enough pts sessions, this is also
easy to update.

Steven

[ Post a follow-up to this message ]

Ian Wilson <scobloke2@infotop.co.uk> wrote in message news:<c3efbm$qus$1@titan.btinternet.c
om>...
> david wrote: 
>
> Why not amend the login scripts thusly
>
> if (already a session on this tty)
>    echo You are already logged in. Max one session per terminal.
>    sleep 3
>    exit
> end if
>
> (assuming they have the pseudo-code shell as their login shell :-)
>
> I'd dress it up by creating a lock file (probably in /tmp) and catching
> interrupts to ensure it is deleted at end of session.
>
> YMMV, Batteries not included.
thanks guys for all the helpful information..i passed this on to my
boss..this is her reply
"I read the threads so far, the script sounds logical, but I don't
know if I
dare to mess with the scripts.  I only know the very basics of AIX.
The
duplicates are the smallest of the problem, the licenses get used up
because
everyone that has the program logs in and then sits idle all day.  I
do see
duplicates on the front desk occasionally, but it usually only
accounts for
about 4 to 6 extra users."

seems like its the managers not the front desk sessions that are
causing the problems..the managers start a terminal session to run
reports and then leave this session idle...how bout running a script
on the terminal emulator (we use qvt term) that logs off user after a
certain time..or any other advice?..thanks in advance guys...David

[ Post a follow-up to this message ]

On 21 Mar 2004 05:23:27 -0800, david <maine666@hotmail.com> wrote:

> seems like its the managers not the front desk sessions that are
> causing the problems..the managers start a terminal session to run
> reports and then leave this session idle...how bout running a script
> on the terminal emulator (we use qvt term) that logs off user after a
> certain time..or any other advice?..thanks in advance guys...David

Gets back, then, to training and/or a license manager timeout.  What
license manager does this program use?  Talk to the vendor & explain
the problem, and ask them what their solution is.  You can't be
the first user of their product to run into this, right?

If they don't have a solution for you, I think you're back to scripting,
but you could check to see where the job is open & kill idle instances.
Put up a banner saying it was killed so they don't think it's just
happening for no reason.

A thought - why are they always opening it up and leaving it open?  Is
it really slow to start, or is this just one of those cultural things
of "Well, we always do it that way"?  If the former, it's tougher to
fix.  If the latter, then it's back to training and/or forcing the
issue.

Dave Hinz

[ Post a follow-up to this message ]