James.Q.L wrote:
my apology.
i was thinking that was a problem with mod_perl somewhere in my code since the same
snmp query
result is the same as the next one.
It's possible, but you haven't even mentioned that you were running mod_perl
;). Have you tried running that code as a standalone progra
my apology.
i was thinking that was a problem with mod_perl somewhere in my code since the same
snmp query
result is the same as the next one.
Qiang
--- Stas Bekman <[EMAIL PROTECTED]> wrote:
> James.Q.L wrote:
> > Hello,
> >
> > i am using snmp and alarm together to timeout a snmp query(
James.Q.L wrote:
Hello,
i am using snmp and alarm together to timeout a snmp query( to printer ).
are you sure you wanted to send this to the modperl list?
Please find an appropriate list at: http://lists.perl.org/
thanks.
__
Stas
Charlie Smith wrote:
In transitioning to mod_perl 1.99_13 I have a couple question. Today, I got
mod_perl built into Apache 2.
However, I would expect to be able to actually get the mod_perl working.
I used to be able to see if it was actually running by looking at the
GATEWAY_INTERFACE. (r
Hello,
i am using snmp and alarm together to timeout a snmp query( to printer ). however,
once a timeout
happens with an alarm, the next snmp query with a different snmp session always
inherit the
previous failed snmp query result. i also use the timeout property in snmp, but it
doesn't seem t
> What are the proper directives for replacing the following lines in the Apache
> 1.3.28 config file?
> PerlModule Apache
> PerlModule Apache::Registry
>
> I would assume something like:
> PerlModule ModPerl
you don't need that. but you might need
PerlModule Apache2
if you had an existing
In transitioning to mod_perl 1.99_13 I have a couple question. Today, I got
mod_perl built into Apache 2.
However, I would expect to be able to actually get the mod_perl working.
I used to be able to see if it was actually running by looking at the
GATEWAY_INTERFACE. (reference: to see GATE
Jean-Michel Hiver wrote:
> Hi List,
>
> When doing the following:
>
> * Using Apache::Registry
> * Using PerlSendHeader On
> * Sending a custom 404 Not Found response from the Apache::Registry script
>
> I get a very strange behavior. In the response, Apache sends:
>
> * the custom 404 header
Swen Schillig wrote:
I figured a few strange outputs while running make test
after a successful compilation of mod_perl-1.99-13
saying that
the server couldn't be started (syntax error at line 27 of
httpd.conf -> Listen localhost:8xxx) (Linux on i386)
or
dubios output for most of t
Hi List,
When doing the following:
* Using Apache::Registry
* Using PerlSendHeader On
* Sending a custom 404 Not Found response from the Apache::Registry script
I get a very strange behavior. In the response, Apache sends:
* the custom 404 headers PLUS
* the custom 404 html generated by the scri
I've done a search through the archives, and the only related question I
could find didn't include any conf. information.
'
I thought I had my httpd.conf configured correctly for
Apache::AuthCookieDBI. the same ( well, close to the same ) setup
worked for Apache::AuthCookie
the error message:
Brett Randall wrote:
On 11 Mar 2004, Perrin Harkins wrote:
As Skylos also pointed out, a common approach for handling these
things is to have a singleton class. If that sounds too confusingly
OO for you, just think of a simple utility function that you always
call to get a $dbh:
Wow... Perrin..
Nice! It all worked now. It's odd how the page said this problem would be
fixed in version 2.0 =)
Thanks for your help,
Nath
- Original Message -
From: "Perrin Harkins" <[EMAIL PROTECTED]>
To: "Nath" <[EMAIL PROTECTED]>
Cc: <[EMAIL PROTECTED]>
Sent: Thursday, March 11, 2004 1:17 AM
Subje
I figured a few strange outputs while
running make test
after a successful compilation of mod_perl-1.99-13
saying that
the
server couldn't be started (syntax error at line 27 of httpd.conf ->
Listen localhost:8xxx) (Linux on i386)
or
dubios
output for most of the tests (Linux on PP
Hi everyone,
Compared to some of the questions posted here, I'm still a relative
newbie with mod_perl. However, I rememeberd something here. Reading:
http://perl.apache.org/docs/2.0/api/Apache/Reload.html
the Synopsis lists this:
# Monitor and reload all modules in %INC:
# httpd.conf:
The problem is fixed by upgrading to perl 5.8.3. I was using 5.8.0.
Rick
On Thu, Mar 11, 2004 at 12:26:48AM -0800, Stas Bekman wrote:
> Rick Jansen wrote:
> >Hi,
> >
> >I'm trying to run a little test script here under mod_perl.
> >When I request the script, all apache childs die with sig11:
>
>
On 11 Mar 2004, Perrin Harkins wrote:
> As Skylos also pointed out, a common approach for handling these
> things is to have a singleton class. If that sounds too confusingly
> OO for you, just think of a simple utility function that you always
> call to get a $dbh:
Wow... Perrin... That seems to
Rick Jansen wrote:
Hi,
I'm trying to run a little test script here under mod_perl.
When I request the script, all apache childs die with sig11:
Report problems: http://perl.apache.org/bugs/
__
Stas BekmanJAm_pH --> Jus
Hi,
I'm trying to run a little test script here under mod_perl.
When I request the script, all apache childs die with sig11:
[Thu Mar 11 09:04:39 2004] [notice] child pid 957 exit signal
Segmentation fault (11)
[Thu Mar 11 09:04:39 2004] [notice] child pid 1009 exit signal
Segmentation fault (11)
19 matches
Mail list logo
