Kenneth:
Thanks for the help. I haven't changed from whatever the default is; I
copied RT_Config.pm to RT_SiteConfig.pm and made some local changes.
From there the setting appears to be DB, as ::File is commented out:
# $WebSessionClass is the class you wish to use for managing Sessions.
# It defaults to use your SQL database, but if you are using MySQL 3.x and
# plans to use non-ascii Queue names, uncomment and add this line to
# RT_SiteConfig.pm will prevent session corruption.
# Set($WebSessionClass , 'Apache::Session::File');
Yitzchak Schaffer
Systems Librarian
Touro College Libraries
33 West 23rd Street
New York, NY 10010
Tel (212) 463-0400 x230
Fax (212) 627-3197
[EMAIL PROTECTED]
Kenneth Crocker wrote:
Yitzchak,
I have just gone thru this problem. Believe it or not, it is easy
to fix. The answer came to me from someone who uses RT and is an
Apache expert. You need to specify a tighter control (Transaction)
over your session locks. Are you using the DataBase session record or
file?
_______________________________________________
http://lists.bestpractical.com/cgi-bin/mailman/listinfo/rt-users
Community help: http://wiki.bestpractical.com
Commercial support: [EMAIL PROTECTED]
Discover RT's hidden secrets with RT Essentials from O'Reilly Media.
Buy a copy at http://rtbook.bestpractical.com
