Hello there-
I am working on a project that is bigger than a single host. As a result I have sessions logging into several hosts but working out of a common (nfs mounted) directory. Specifically things are operating using a single, comon (shared) state directory... is this bad?? I am running into situations where the state directory gets corrupted and processes "hang" until the state directory gets cleared (removed) at which time things will run ok for awhile until it hoses up again. The biggest thing that seems to cause problem is that the secure server is on a separate host from the rest of the site-- and yet it too operates using the common state directory. I most often see problems when going back and forth to the secure server from the main parts of the site. In general, the site runs just fine on its own, meaning on one server or another. Also, I've worked hard to have mirror environments (same user/group ids, perl modules available, same binaries, etc) running between identical servers. I suspect this last bit is not the most important thing. I further suspect that my biggest problem is somehow related to the shared state directory. Yet, if I cannot use a common state directory, how am I to recognize an account that has logged into server-A and is now attempting to work with server-B? Thanks for any assistance. John Whitten [EMAIL PROTECTED] Wizard.Org, Inc. BTW: Thanks Joshua for your work on mysterious server failures-- it would have taken me a zillion years to think of renaming common modules in different sites. --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
