On Aug 25, 2006, at 02:19, Jesse Vincent wrote:
Can you try using /opt/rt3/bin/standalone_httpd? That will let us tell
if it's apache/mod_perl or perl itself.
OK, I tried this (stopped the apache httpd to make sure it was coming
in to the standalone_httpd), same results.
-Bill
-
Bill
See the message I posted to rt-users yesterday. Upgrade CGI.pm
On Sat, Aug 26, 2006 at 09:40:00PM -0400, Bill McGonigle wrote:
On Aug 25, 2006, at 02:19, Jesse Vincent wrote:
Can you try using /opt/rt3/bin/standalone_httpd? That will let us tell
if it's apache/mod_perl or perl itself.
On Aug 24, 2006, at 23:51, Jesse Vincent wrote:
We're seeing this all over the place. with redhat based systems.
OK, good to know it's not just me.
Just to eliminate one thing we've changed in the past couple weeks,
could you install:
On Fri, Aug 25, 2006 at 01:59:24AM -0400, Bill McGonigle wrote:
On Aug 24, 2006, at 23:51, Jesse Vincent wrote:
We're seeing this all over the place. with redhat based systems.
OK, good to know it's not just me.
Just to eliminate one thing we've changed in the past couple weeks,
Hi, Folks,
I'm trying to figure out why a new RT 3.6.1 install (fc3, postgresql
7.4.11, modperl2, perl 5.8.5, apache 2.0.53, postfix 2.1.5) isn't doing
reply-to-requestors or comments from the web interface. The output
html starts with a /div tag and includes the number of msec the
On Thu, Aug 24, 2006 at 11:29:09PM -0400, Bill McGonigle wrote:
Hi, Folks,
I'm trying to figure out why a new RT 3.6.1 install (fc3, postgresql
7.4.11, modperl2, perl 5.8.5, apache 2.0.53, postfix 2.1.5) isn't doing
reply-to-requestors or comments from the web interface. The
