Ken Perl am Dienstag, 7. Februar 2006 07.44:
> when Apache::DB is initialized it will write a line of log into
> error.log, but without a timestamp,
> [notice] Apache::DB initialized in child 1957
> May I add one?
>
> --
> perl -e 'print unpack(u,"62V5N\"FME;G\!E ")'
yes, by putting the line
use
when Apache::DB is initialized it will write a line of log into
error.log, but without a timestamp,
[notice] Apache::DB initialized in child 1957
May I add one?
--
perl -e 'print unpack(u,"62V5N\"FME;G\!E
Daniel McBrearty wrote:
If I have a library which is used for both mod_perl and standard cgi
processes, and I want to know at runtime which, how can I do that?
does ARGV[0] tell you? I'd expect it to be 'httpd' for apache/modperl.
If I have a library which is used for both mod_perl and standard cgi
processes, and I want to know at runtime which, how can I do that?
thanks
Daniel-- Daniel McBreartyemail : danielmcbrearty at gmail.comwww.engoi.com : the multi - language vocab trainerBTW : 0873928131
On 2/6/06, Ben Kim <[EMAIL PROTECTED]> wrote:
> 1. Are the permissions right?
when launching apache as root, permissions aren't very significant, are they?
> 2. Just curious, by any chance did you update mod_perl from 1.99xxx to
> 2.0?
this was on a fresh debian setup:
apt-get install apache2-
On Feb 6, 2006, at 4:06 PM, Peter Klump wrote:
I'm having a problem with my perl scripts after I ported them into
a new
server environment.
My server environment:
Apache2 2.0.55
Perl 5.8.3
CGI 3.15
mod_perl 2.0.2
What is happening is that _occasionaly_ (maybe 1 out of 20 times)
the POST
da
Hi list,
I'm having a problem with my perl scripts after I ported them into a new
server environment.
My server environment:
Apache2 2.0.55
Perl 5.8.3
CGI 3.15
mod_perl 2.0.2
What is happening is that _occasionaly_ (maybe 1 out of 20 times) the POST
data users send by their browser to my perl sc
On Mon, 6 Feb 2006 22:25:34 +0800
Ken Perl <[EMAIL PROTECTED]> wrote:
> Hi,
> I configured Apache::DB in my modperl2 and got a notice message in
> apache2 startup error.log,
> [notice] Apache::DB initialized in child 1123
>
> I think I have setuped it successfully.
> And I also see the debugger w
I'm not a guru in gdb and with stack traces but some guesses!
Did you tried it with a recent perl compiled by your own and not the
stock perl from debian.
I always compile perl myself because most distros ship with a threaded
perl (and so does debian) which is not needed when e.g. running apache
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Hi Tom,
thanks for the hint. I always tried out one self compiled mp2 2.0.2
and got the same segfault with exactly the same
backtrace in gdb.
- --
Dave
Am 06.02.2006 um 15:10 schrieb Tom Schindl:
Hi David,
sorry to disappoint you here but ve
On 2/6/06 9:06 AM, "Ken Perl" <[EMAIL PROTECTED]> wrote:
> Yes, I am using Apache2, the doc is very useful.
> in httpd.conf file, I use PerlInitHandler example.pm's handler() as
> starting point, when I update the code in handler(), I didn't see the
> updates, so I asked previous question.
> Af
Ken Perl wrote:
> Hi,
> I configured Apache::DB in my modperl2 and got a notice message in
> apache2 startup error.log,
> [notice] Apache::DB initialized in child 1123
>
> I think I have setuped it successfully.
> And I also see the debugger welcome message,
> Loading DB routines from perl5db.pl
Hi,
I configured Apache::DB in my modperl2 and got a notice message in
apache2 startup error.log,
[notice] Apache::DB initialized in child 1123
I think I have setuped it successfully.
And I also see the debugger welcome message,
Loading DB routines from perl5db.pl version 1.28
Editor support avail
Hi David,
sorry to disappoint you here but version 1.9921 is a preview release of
mp2 and not marked stable. At the moment we have 2.0.2, I know that
1.9921 is the version debian ships with but to get support you'll
certainly have to upgrade your mp2 to an offically stable release, maybe
debian do
Yes, I am using Apache2, the doc is very useful.
in httpd.conf file, I use PerlInitHandler example.pm's handler() as
starting point, when I update the code in handler(), I didn't see the
updates, so I asked previous question.
After I read the head of the doc, I make sense that I need to modify
the
Hello,
After upgrading from apache 1.3 to apache 2.0 I run into problems
with the DBILogger.pm
This packages is used to insert logging informations into a mysql
database.
To work together with the new mod_perl2 api I did lightly changes to
the DBILogger.pm (attached below).
I installed
hello,
it's not so exact from your words.when your main script change,there is no need
to reload or restart httpd.
only when you 'use' or 'require' modules in your main script,and then the
modules have changed,it need to restart the httpd.
when your modules changed,you could use 'Apache::Reload'
On 2/6/06 7:10 AM, "Ken Perl" <[EMAIL PROTECTED]> wrote:
> When code is updated during developing period, httpd progress must be
> reload or restart so that to see the change. If is it possible to see
> the change without reload httpd?
You didn't say which version of mod_perl you are using, but
When code is updated during developing period, httpd progress must be
reload or restart so that to see the change. If is it possible to see
the change without reload httpd?
--
perl -e 'print unpack(u,"62V5N\"FME;G\!E
19 matches
Mail list logo
