I'm doing this by putting the Simultaneous-Use option in my database as a
check item. That way, each user gets their own sim-use setting. My
software is setup to give them 1 by default, but a change to the db can
give them whatever I need. That way, I don't have any Simultaneous-Use
option for the DEFAULT user - it comes completely out of the db (which I
use for Authing and I use AuthSelect statement that pulls the Sim-Use
number out along with the Encrypted Password.) Since my DEFAULT user
doesn't have the check item, there is no "most restrictive" setting to
match.
--------------------------------------------------------------------------
Aaron Holtz
ComNet Inc.
UNIX Systems Specialist
Email: [EMAIL PROTECTED]
"It's not broken, it just lacks duct tape."
--------------------------------------------------------------------------
On Mar 22, Stephen Roderick molded the electrons to say....
>On Mon, 22 Mar 1999, True Communications Corp. wrote:
>
>> defined to 1 as the default for all users in the users file. I was under the
>> impression
>> that you can override the default for any of the users by using the
>> Simultaneous-Use
>> attribute in the users file. Which is exactly what I did.
>
>Wouldn't that be nice. Unfortunately it doesn't work that way. It uses the
>MOST restrictive setting.
>
>I would really love to have a "DefaultSessionMax" or something. That meant
>without a specific Sim-Use setting use the default. Then the sim-use
>setting would OVERRIDE the default.
>
>Much better. :-)
>
>Steve
>
>
>===
>To unsubscribe, email '[EMAIL PROTECTED]' with
>'unsubscribe radiator' in the body of the message.
>
===
To unsubscribe, email '[EMAIL PROTECTED]' with
'unsubscribe radiator' in the body of the message.
