On 12/20/06, Philip Kime <[EMAIL PROTECTED]> wrote:
Running mysql 5 under RT with a master/slave configuration and I would like
to be able to make one of the slaved read-only. This is impossible using RT
rights because that means altering the database on the slave which
eventually (or quickly ...) breaks mysql replication because of duplicate
IDs in the RT transaction table. Starting Mysql on the slave "read-only"
would be nicer but RT won't start at all in this case because it complains
about not being able to write session data. It mentioned
/usr/local/rt/var/session_data. Is there any way to force RT to use the
filesystem locations for session data etc. so that the DB can be completely
read-only?
Look into config. Change session class to Apache::Session::File.
PK
--
Philip Kime
NOPS Systems Architect
310 401 0407
_______________________________________________
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
--
Best regards, Ruslan.
_______________________________________________
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
