John Madden wrote:
- User 1 logs in to webserver 1, gets session id abc123
- User 2 logs in to webserver 2, gets session id abc123 and trashes current contents of abc123 session file
If using NFS as the session store, you don't even have to get this specific -- one user using "his" session from two servers simultaneously will eventually see problems.
Isn't that an argument not to use LVS persistence?
Oh, here's another example that just came to mind. It didn't happen under SQM 1.2.x, but under 1.4.x with NFS-shared userprefs files, I observed the entire file being lost and started from scratch. I was able to cause this to happen a couple dozen times without finding out exactly what was causing it, but it seems consistent with what we've been discussing. That prompted a quick switch to SQL-based prefs.
This sometimes happens in single server environments when users log in to two different SM accounts in the same browser (but different windows) at the same time. It could have been that problem, or it could have been another way to hit the same root cause (which hasn't been easy to track). It's interesting that SQL-based prefs made this go away for you (so maybe it's not the same problem...)
------------------------------------------------------- SF.Net email is sponsored by: Tell us your software development plans! Take this survey and enter to win a one-year sub to SourceForge.net Plus IDC's 2005 look-ahead and a copy of this survey Click here to start! http://www.idcswdc.com/cgi-bin/survey?id=105hix -- squirrelmail-users mailing list Posting Guidelines: http://squirrelmail.org/wiki/wiki.php?MailingListPostingGuidelines List Address: [email protected] List Archives: http://news.gmane.org/thread.php?group=gmane.mail.squirrelmail.user List Archives: http://sourceforge.net/mailarchive/forum.php?forum_id=2995 List Info: https://lists.sourceforge.net/lists/listinfo/squirrelmail-users
