server startup shutdown

[dima]

I have XML  file
and don`t want parse/serialize on each request
how implement this:
1) XML parsed on startup
2) All modules work whith same object
3) XML serialize on server shutdown


P.S. Apache 2 mod_perl 2

Session managing using PerlTransHandler

[dima]

How I Can redirect to page http://foo.bar/ses1/index.html from  PerlTransHandler 
Module?

Re: Segfault: apache-1.3.17+modperl-1.25

[dima]

Hmm,
 have you built mod_perl with PERL_USELARGEFILES=0?

 I've got almost the same set up (RH7) running just fine.

On Wed, 14 Feb 2001, Gary Algier wrote:

 My children are segfaulting.

 I have:
   Solaris 2.6 (w/all latest patches installed right after the OS)
   Perl 5.6.0 (no largefiles, no threads)
   Apache 1.3.17
   modperl 1.25 (as a DSO)
   gcc 2.95.2 (using Sun's as and ld)

 If I run apache leaving out:
   LoadModule perl_modulelibexec/libperl.so
   AddModule mod_perl.c
 it runs just fine.  Put them in and the child seg faults.   I did manage
 to gdb the process and it says:

 Program received signal SIGSEGV, Segmentation fault.
 0xef0a2e00 in perl_header_parser ()
 (gdb) where
 #0  0xef0a2e00 in perl_header_parser ()
 #1  0x20714 in run_method ()
 #2  0x208e4 in ap_header_parse ()
 #3  0x3d9bc in process_request_internal ()
 #4  0x3ded0 in ap_process_request ()
 #5  0x314c8 in child_main ()
 #6  0x31854 in make_child ()
 #7  0x31dcc in perform_idle_server_maintenance ()
 #8  0x32630 in standalone_main ()
 #9  0x32f64 in main ()

 Unfortunately, there are no debugging symbols so it is limited.  It wasn't
 easy getting this, though if it would help I will endeavor to rebuild
 everything with debugging symbols and try again.

 In general, I know that DSOs are working as I runtime load the max.  I also
 load php 4.0.4pl1 that way and it works.

 Any ideas?  Does the trace help?



 --
 Gary Algier, WB2FWZ   [EMAIL PROTECTED]   +1 856 787 2758
 Ulticom Inc., 1020 Briggs Rd, Mt. Laurel, NJ 08054  Fax:+1 856 866 2033

A self-addressed envelope would be addressed "envelope."

Re: Error reporting mod_perl 1.25 + apache 1.3.17

[dima]

I used to have all these seg faults when dealing with apache1.3.14 and
mod_perl1.24_01 (perl5.6.0/redhat 6.2) when built as DSO. As soon as you
get a request through log files just get flooded with segmentation faults.
 However when I switched over to apache1.3.17 + mod_perl1.25 everything
goes on just fine.
 Try using PERL_USELARGEFILES=0 when building mod_perl too.

cheers,
dima

On Mon, 5 Feb 2001, modperl wrote:

 Actually My current builds are very similar. 1.3.17+1.25w/5.6.0 on
 slackware linux 7.1, dually intel boxes.
 Works fine and while watching error logs i haven't seen any
 segfaults. returns our pages just fine.

 Scott

 On Mon, 5 Feb 2001, Paul Lindner wrote:
  On Mon, Feb 05, 2001 at 06:41:00PM +, G.W. Haywood wrote:
   Hi there,
   On Mon, 5 Feb 2001, Matisse Enzer wrote:
I compiled perl 5.6 and Apache 1.3.17 using gcc egcs-2.91.66
on a RH Linux 6.1 system.
   I'm sure there must be people on this List who have successfully built
   mod_perl systems using exactly the packages you have mentioned.
   Anyone care to confirm that?
  I've seen some strange segementation fault problems with mod_perl
  1.25.  I have not had the time to document these.
  Environment is similar to others: mod_perl 1.25, apache 1.3.17, perl
  5.00503, solaris 2.6...