It is spiffy, but it's doesn't periodically check with the hub to see who's logged on (at least it doesn't in my version, I am running one rev back). Only when it's about to deny someone a login because they are exceeding their max session count does it go out and look to see if the other sessions are still up. Since radiator is single threaded, I'd think this could really cause a problem if the check is slow or hangs.
Aaron, Are you using Radiators session database to limit your concurrent sessions of your users? does it work well? I use Radiator. But for concurrency I use tsmon, just because thats how I started. I may use radiators session database in time though. Their are alot of cool things you can do with Radiator, I love it. Brian
-- Aaron Nabil
- To unsubscribe to usr-tc, send an email to "majordomo@xmission.com" with "unsubscribe usr-tc" in the body of the message. For information on digests or retrieving files and old messages send "help" to the same address. Do not use quotes in your message.
----------------------------------------------------- Brian Feeny (BF304) signal@shreve.net 318-222-2638 x 109 http://www.shreve.net/~signal Network Administrator ShreveNet Inc. (ASN 11881) - To unsubscribe to usr-tc, send an email to "majordomo@xmission.com" with "unsubscribe usr-tc" in the body of the message. For information on digests or retrieving files and old messages send "help" to the same address. Do not use quotes in your message.