On Mon, 5 Feb 2001 [EMAIL PROTECTED] wrote:
Sometime in the next month I need to embark on a log analyzer for the logs
we've been accumulating for many moons via Apache::DBILogger. Has anyone
made any effort to do such a thing already? I've dug around the web for a
while and come up with
In local.modperl you write:
What is the "official" home of 5.6.1rev2? I can't seem to locate it on
CPAN anywhere. The p5p summary on http://www.perl.com/ seems to be under
the impression that 5.6.1 isn't going to be out for a while. I remember
seeing a pointer to one of the very early patches,
How do i change this locking mechanish of win32?
Am i using the wrong module? From apache::session::* modules
do you know which are supposed to work on win32?
Thanks
Gunther Birznieks wrote:
You need to change the locking mechanism on Win32 to not use IPC. I believe
there are examples for
Subject: Help: Can't use string ("Exchange::Account::My") as
a HASH ref
while "strict refs" in use trying to use instance variables in my
handler
[snip]
sub handler ($$) {
my ($self, $q) = @_;
my $r= Apache::Request-new($q);
$self-child_init unless
I have set this up with our Oracle Database, but I am not getting
anything in the database nor am I getting any errors. Everything
still seems to log to the log files?
If errors are being generated, where would I find them? Any way to
trace through and see what is happening?
--
C Wayne
On Tue, 6 Feb 2001, T.J. Mather wrote:
I have a script that reads the logs from the database and dumps it out
to a flat file in the standard format Apache uses when writing
access_log, then I run a program called webalizer on it. I actually
don't use Apache::DBILogger, but the database table
Thank you for that pointer. I checked http://www.pagekit.org/. Looks
very interesting.
While on the subject I'd like to mention another really nice book by
Mark Grand called "Patterns in Java" that might be of interest to those
looking into Design Patterns. This book has many additional pattern
wm looks like a home directory. The default perms on the home
directory are usually 700. Try changing that to something like 755
or even 744 (it may not need execute).
Actually, the x bit on directory perms means "accessible," meaning if you
KNOW the name of the file, U can reach it at
Neither of the following combinations worked for me:
drwx--x--x3 rlandrum devel4096 Jan 30 14:14 public_html
(711, Forbidden)
drwx-x3 rlandrum devel4096 Jan 30 14:14 public_html
(701, Forbidden)
The only one that worked was:
drwxr-xr-x3 rlandrum devel
Hi there,
On Tue, 6 Feb 2001, Shane Adams wrote:
I've found a "write to a dangling pointer" when apache/mod_perl
evaluates a perl section of the apache config file.
My question: How do I go about attacking this problem?
1. Reduce your test case to the absolute minimum.
2. 'perldoc
If you're looking for which piece of perl code being processed, there
are some gdb macros to help. If you source the .gdbinit in the root of
your modperl dir you have access to a bunch of cool macros to use. In
this case, curinfo will give you the current line number in your perl
code.
here's
Title: RE: Debugging mod_perl with gdb
Hey thanks. I'll try this. I tried the 'man gdb' command and it didn't help much I'm afraid...
-Original Message-
From: sterling [mailto:[EMAIL PROTECTED]]
Sent: Tuesday, February 06, 2001 12:33 PM
To: Shane Adams
Cc: [EMAIL PROTECTED]
Subject:
Anyway, what you should do is create a constructor:
sub new {
my $class = shift;
my $self {@_};
bless $self, $class;
return $self;
}
You mean like this code segment that I included in my original post
just below the handler code :)
sub init {
my $invocant = shift;
my $class
"RL" == Robert Landrum [EMAIL PROTECTED] writes:
RL Under Linux, 'x' does mean execute... from the chmod manpage
RL The letters `rwxXstugo' select the new permissions for the
RL affected users: read (r), write (w), execute (or access
RL for directories) (x), execute
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
-Original Message-
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED]] On Behalf Of
Matthew Schroeder
Sent: 05 February 2001 21:13
To: '[EMAIL PROTECTED]'
Subject:Apache::ASP Best Language to use?
Currently the company I work for is using ASP code running on Windows
Hi again,
On Tue, 6 Feb 2001, Shane Adams wrote:
I tried the 'man gdb' command and it didn't
help much I'm afraid...
Then why not have a look at
http://www.gnu.org/manual/gdb-4.17/gdb.html
I'm not a great fan of using debuggers, but as they go it's fantastic,
it's really worth getting to
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
I sent this to the Template Toolkit list but got no responses. I'm
pretty sure it is a mod_perl issue, but I can't for the life of me
figure out why the object doesn't get destroyed in the mod_perl
context. A standalone test program always destroys the object at the
expected time.
This bug
execute (or access
for directories) (x)
drwx-x3 rlandrum devel4096 Jan 30 14:14 public_html
(701, Forbidden)
that's not what I meant, I should have been more clear.
755 on public_html
701 on ~user
so ~user is still "hidden" from general eyes
but
Thanks for the clarification. It worked perfect.
drwx-x 12 rlandrum rlandrum 4096 Feb 6 14:05 rlandrum
drwxr-xr-x3 rlandrum devel4096 Jan 30 14:14 rlandrum/public_html
Rob
execute (or access
for directories) (x)
drwx-x3 rlandrum devel
Vivek Khera ([EMAIL PROTECTED]) said something to this effect on 02/06/2001:
However, at the end of the template processing, the object is not
destroyed; that is, the DESTROY() method is never called, and
therefore the tied hash never gets untied and Apache::Session::MySQL
doesn't get a
On Tue, 6 Feb 2001, Vivek Khera wrote:
However, at the end of the template processing, the object is not
destroyed; that is, the DESTROY() method is never called, and
therefore the tied hash never gets untied and Apache::Session::MySQL
doesn't get a chance to write the data back to the
On Tue, 6 Feb 2001, darren chamberlain wrote:
Vivek Khera ([EMAIL PROTECTED]) said something to this effect on 02/06/2001:
However, at the end of the template processing, the object is not
destroyed; that is, the DESTROY() method is never called, and
therefore the tied hash never gets
I am getting errors when I try and run ASP on my Linux box...
Here is what pops up on the web page, I am not sure how to fix it or
what exactly is wrong with it. Any help you can offer will be
appreciated..
#!/usr/local/bin/perl5 asp [0]% ([0]%source)
Thanks,
Paul Scott
[EMAIL PROTECTED]
I'm jazzed to announce the public release of OpenInteract, an
extensible web application framework using mod_perl and the Template
Toolkit as its core technologies. But the README already does all the
heavy lifting:
WHAT IS IT?
=
OpenInteract is an extensible
Chris Winters wrote:
I'm jazzed to announce the public release of OpenInteract, an
extensible web application framework using mod_perl and the Template
Toolkit as its core technologies.
Hi Chris,
I've been reading the docs for the last couple of days and it looks very
interesting. It's
* Perrin Harkins ([EMAIL PROTECTED]) [010206 22:43]:
Hi Chris,
I've been reading the docs for the last couple of days and it looks very
interesting. It's great to see a well-documented open source project.
I have a couple of specific questions, which I guess are really about
SPOPS more
* L.M.Orchard ([EMAIL PROTECTED]) [010207 00:07]:
So, I'm trying to install OpenInteract now since from 50,000 ft it sounds a
lot like what I was trying to do with Iaido. Using Template Toolkit for the
presentation... abstracted data management... Need to look around more.
I'd be more
Hello modperl,
There is Apache Perl module, which uses File::Cache.
File::Cache object is initialized in every request with params
namespace PRTL
max_size 10485760
expires_in 86400
cache_depth 3
Cache size after 24 hours of working
via 'du -s' - 53M
via 'perl -MFile::Cacje -e"print
30 matches
Mail list logo
