stas        2004/10/02 07:43:43

  Modified:    src/docs/1.0/guide troubleshooting.pod
  Log:
  print() doesn't send anything on Mac OS X
  Submitted by: Charlie Garrison <[EMAIL PROTECTED]>
  
  Revision  Changes    Path
  1.30      +16 -0     modperl-docs/src/docs/1.0/guide/troubleshooting.pod
  
  Index: troubleshooting.pod
  ===================================================================
  RCS file: /home/cvs/modperl-docs/src/docs/1.0/guide/troubleshooting.pod,v
  retrieving revision 1.29
  retrieving revision 1.30
  diff -u -u -r1.29 -r1.30
  --- troubleshooting.pod       12 Sep 2004 19:14:44 -0000      1.29
  +++ troubleshooting.pod       2 Oct 2004 14:43:43 -0000       1.30
  @@ -429,6 +429,22 @@
   
   =head1 Runtime
   
  +
  +
  +
  +
  +=head2 print() doesn't send anything on Mac OS X
  +
  +On certain Mac OS X builds mod_perl doesn't seem to able to print()
  +anything to the client. That's because C<STDOUT> is not tied to the
  +C<Apache> module. Most likely some core module on Mac OS X
  +untie's/re-tie's C<STDOUT> after mod_perl had it tied. The workaround
  +is to add:
  +
  +  PerlHeaderParserHandler "sub { tie *STDOUT, 'Apache' unless tied *STDOUT; 
}"
  +
  +
  +
   =head2 "exit signal Segmentation fault (11)" with mysql
   
   If you build mod_perl and mod_php in the same binary, you might get
  
  
  

---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Reply via email to