> > Ok - I've done that. The SES: message always comes from the > parent process so it is not always easy to match the SESSION > data to the child process that is actually performing the request. >
The question is, what are you seeing in case of the problem you have. Could you quote the SES: messages from the log for this case? > I am wondering if my problems may be caused by using the > stock threaded perl even though we are using the old prefork > method with Apache 2.0? My server specs are below, but please add: > SessionX = $VERSION = '2.00b5' > SESSION = $VERSION = '1.6' > Threaded Perl is ok, as long as Apache is prefork. > Thanks, > > Cliff > On Wed, September 14, 2005 12:59 am, Gerald Richter said: > > Could you turn on dbgSession and see what session related entries > > appear in the embperl.log? > ----- snip----- > >> > >> --------------------- > >> Server specs: > >> > >> Fedora Core release 1 (Yarrow) > >> perl, v5.8.3 built for i386-linux-thread-multi > >> mod_perl/1.99_12 > >> Embperl 2.0b11 > >> Apache/2.0.50 > >> > ----- snip ----- > > _____cliff_rayman_____________________________________ > Business Consulting and Turnaround Management [web] > http://www.rayman.com/ [web] > http://all-clear-turnaround-management.com/ > [eml] cliff -AT- rayman.com > [phn] 888-736-3802 x701 > [fax] 818-743-7404 > ______________________________________________________ > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > > --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
