(ASCEND) 6.1 Missing Stop Records

[Glen Browley <gwb@globility.com>]

I think I have discovered a major problem with the 6.1 code. We use a 
MySQL database to record information about users connect times, prevent 
multiple logins, etc. Up until now everything has been working fine but 
as soon as I upgraded a couple of my maxen to the 6.1 code I noticed that 
a lot of users where getting stuck in the database (the database reads 
the stop records to clean out the users once they logout) and couldn't 
log back in (no multiple logins). Once I downgraded these maxen back to 
the closed beta code the problem went away. Also, the remaining maxen 
running 6.0.X are also fine.

Anyone know what's up with this?

Matt? Kevin?

Sincerely, 
 
Glen Browley
System Administrator
Globility Online Inc.
Email: gwb@globility.com
_____________________________________________________
ADDRESS: 2 Valleybrook Drive, Don Mills, ONT  M3B 2S9 
TEL: 416.385.0459 	           FAX:  416.385.0469

++ Ascend Users Mailing List ++
To unsubscribe:	send unsubscribe to ascend-users-request@bungi.com
To get FAQ'd:	<http://www.nealis.net/ascend/faq>

---

Follow-Ups:

• Re: (ASCEND) 6.1 Missing Stop Records
• From: iml@interconnect.net

References:

• Re: (ASCEND) 6.1 clarifications
• From: Jason Nealis <nealis@babylon.erols.com>

---

• Prev by Date: Re: (ASCEND) 6.1 Missing Stop Records
• Next by Date: Re: (ASCEND) 6.1 clarifications
• Prev by thread: Re: (ASCEND) 6.1 clarifications
• Next by thread: Re: (ASCEND) 6.1 Missing Stop Records
• Index(es):
  • Main
  • Thread