There are no userreferences in any URLs. There never has been.


  _____

From: Roland Dumas [mailto:[email protected]]
Sent: Tuesday, October 23, 2012 8:27 PM
To: [email protected]
Subject: Re: TeraScript-Talk: config file



On Oct 23, 2012, at 10:29 AM, WebDude <[email protected]> wrote:


Hi Folks,

I have several versions of Tera and the old Witango running on several
boxes. The one box I am concenred about, unfortunately, is running an old
version of Witango (2000 but fully patched with the lastest). I am wondering
if one of you kind souls who have been around for a while could take a look
at the config file to see if I am missing something. We are starting to get
thread lock when the server gets busy. I have been pulling my hair out and
trying to make it break myself but cannot find anything. I am most
concwerned with memory vs what I have set up. I have actually seen the same
userreference assing to 2 users from different IP addresses... not sure waht
is going on. The box is running MS 2008 server web edition with 8 gigs of
ram. It is the only thing we are running on the box. The DB is on another
box running MSSQL 2008. Following is what I have. I am most concerned with
cache settings, datasourcelife, itembuffersize, querytimeout, rerquestlimit
and threadpoolsize.




the observation that two visitors are using the same userreference may be a
different animal. You may have a shared (or hijacked) session. This happened
in the ancient days when people left the userreference argument in the URL.
The builders did this by default. If a person had a session going and sent
someone else a URL that contained the userreference, then the recipient
would click on the URL and presto, joined the same session. There were a
couple of other situations that could force this, also. It's a big security
oops.

__




  _____

To unsubscribe from this list, please send an email to
[email protected] with "unsubscribe terascript-talk" in the body.



----------------------------------------

To unsubscribe from this list, please send an email to [email protected] 
with "unsubscribe terascript-talk" in the body.

Reply via email to