I'm just full of problems, now it's a flaky %udat. First the setup. I have 8
developers that are developing off of 1 server, but are using their own apache
processes on different ports. I had to do this way to prevent Perl package sharing
amoungst developers. One problem I ran into was session data. It seemed that the first
developer, to use %udat, had no problems, but the remainders would be locked out.
Instead of using "SysVSemaphoreLocker" or "Semaphore", I used "NullLocker" and "Null"
for the development site. I curious if using the "Null" lock style would cause a
problem with %udat not having values stick.
Little chunck from the httpd.conf.
----
PerlSetEnv EMBPERL_SESSION_CLASSES "MySQL Null"
PerlSetEnv EMBPERL_SESSION_ARGS "DataSource=dbi:mysql:database=sessions
UserName=global Password=global"
----
Thanks,
John
--
John Walstra CNET Networks
Senior Software Developer, Jack Of All Trades 300 Park Blvd, Suite 105
mailto:[EMAIL PROTECTED] Itasca, IL 60143-4914
Phone: 630.438.7000 x1304 Fax: 630.775.0555
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
