i had a problem similar to this, but it didn't have anything to do
with Apache::Session. just incorrect coding on my part. global variables
in the child retain the old data till overwritten by new data. i had missing
clearing or overwriting a global and of couse it contained the wrong data for
the next user.
hth,
--
___cliff [EMAIL PROTECTED]http://www.genwax.com/
Gerald Richter wrote:
> > I use My SQL Semaphore, same setting introduced in the documentation of
> session
> > handling. And what should I do to prevent this happen?
> >
>
> That was only a possibility, I don't know if this is the reason. First of
> all you should see if there is already a name in %udat, when you at your
> login page and you don't expect one. Also you may check if you get errors
> about inserting a duplicate id (id field should be your primary key) in your
> error log. Additionaly you can log the session id and the name somewhere
> (e.g. print LOG "[$$] $udat{_session_id} $udat{name}\n" ; ) to see if
> different users get the same session id, or if the session id changes for
> the same user. Then we could try to work out what goes wrong.
>
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
