On Thu, 6 Dec 2001, Paul Lindner wrote:
BTW -- I think where the docs are cached should be configurable. I don't
like the idea of the document root writable by the web process.
That's the price you pay for this functionality. Because we use
Apache's native file serving code we need a
In article [EMAIL PROTECTED],
Stas Bekman [EMAIL PROTECTED] wrote:
Try to call:
require Fcntl;
instead.
Thanks for the tip. I'm afraid the above verbatim produces the following
error on restart:
| Shutting down http:[ OK ]
| Starting httpd: [Mon
On Tue, Dec 11, 2001 at 01:50:52AM -0800, Ask Bjoern Hansen wrote:
On Thu, 6 Dec 2001, Paul Lindner wrote:
BTW -- I think where the docs are cached should be configurable. I don't
like the idea of the document root writable by the web process.
That's the price you pay for this
[This seems to be a very useful module for those who try to minimize the
memory usage, by finding out irrelevant modules loaded without your
consent :)
Michael G Schwern said:
Module::Use appears to use the let's sniff through %INC approach,
which is clever and useful and sometimes more
Andrew Green wrote:
In article [EMAIL PROTECTED],
Stas Bekman [EMAIL PROTECTED] wrote:
Try to call:
require Fcntl;
instead.
Thanks for the tip. I'm afraid the above verbatim produces the following
error on restart:
| Shutting down http:[
In article [EMAIL PROTECTED],
Stas Bekman [EMAIL PROTECTED] wrote:
Weird, what Perl version are you using? Can you do:
perl -MFcntl -le1
or
perl -le 'require Fcntl'
Both seem to work (producing no output, but no errors either). The
*really* peculiar thing is that actual scripts that
Stas Bekman [EMAIL PROTECTED] writes:
Jorge Godoy wrote:
Stas Bekman [EMAIL PROTECTED] writes:
I think the general advise is to always call require() and not use()
in startup.pl, unless you have a reason for calling certain modules'
import() method.
Wouldn't that affect mod_perl's
On Tue, Dec 11, 2001 at 02:31:36AM -0800, Paul Lindner wrote:
Right. A more elaborate Apache::CacheContent would have a filename
hash function, and a separate cache directory structure along the
lines of Cache::FileCache.
Just curious -- any reason not to use Cache::Cache as the persistance
Howdy!
In my development I neglected to supply the Apache
request object when I called Apache::Request-new( $r ). Actually $r was
undef. It still works! I am just wondering if this is expected behaviour and if
it will be supported going forward or was this just a
fluke?Thanks,
J
Hey Gang,
When using Mail::Sender only the first email is sent on my mod_perl server.
When I investigated, I realised that the socket to the SMTP server was
staying open after the completion of that first email (presumably mod_perl
is responsible for this persistence).
Is there any way to
Wouldn't that affect mod_perl's advantage of sharing the modules? I
mean, would everything be in it's separate namespace and loaded only
once for every module as it is with use?
I don't know about you guys, but I don't feel that sharing the modules
is that much of an advantage. If you write
Paul Lindner wrote:
[snip]
I suppose that one could put the whole uri-cachefile mapping into a
custom PerlTransHandler and leave Apache::CacheContent as-is..
yeah, I think that we're starting to talk about two different
approaches now. the cool thing about the current logic is that no
--On mardi 11 décembre 2001 12:25 + Jonathan M. Hollin
[EMAIL PROTECTED] wrote:
Hey Gang,
When using Mail::Sender only the first email is sent on my mod_perl
server. When I investigated, I realised that the socket to the SMTP
server was staying open after the completion of that first
What version of mod_perl starts supporting this?
Issac
--
Internet is a wonderful mechanism for making a fool of
yourself in front of a very large audience.
--Anonymous
Moving the mouse won't get you into trouble... Clicking it might.
--Anonymous
PGP Key 0xE0FA561B - Fingerprint:
7E18
Issac Goldstand wrote:
What version of mod_perl starts supporting this?
egads, that's old...
looks like 0.95
http://www.bitmechanic.com/mail-archives/modperl/Mar1997/0145.html
--Geoff
When using Mail::Sender only the first email is sent on my mod_perl
server.
When I investigated, I realised that the socket to the SMTP server was
staying open after the completion of that first email (presumably mod_perl
is responsible for this persistence).
Is there any way to defeat the
hi,
Was digging around CPAN looking for a module that would
allow the following..
user is authenticated .. via web.. ok got that..
If they are successful that are
chroot or jailed or caged in a specific
directory which becomes their root..
eg ..
$HOME/public_html
which is ln || lndir to
Andrew Green wrote:
In article [EMAIL PROTECTED],
Stas Bekman [EMAIL PROTECTED] wrote:
Weird, what Perl version are you using? Can you do:
perl -MFcntl -le1
or
perl -le 'require Fcntl'
Both seem to work (producing no output, but no errors either). The
*really* peculiar thing is
[EMAIL PROTECTED] wrote:
hi,
Was digging around CPAN looking for a module that would
allow the following..
user is authenticated .. via web.. ok got that..
If they are successful that are
chroot or jailed or caged in a specific
directory which becomes their root..
eg ..
Jay Lawrence [EMAIL PROTECTED] writes:
In my development I neglected to supply the Apache request object when
I called Apache::Request-new( $r ). Actually $r was undef. It still
works! I am just wondering if this is expected behaviour and if it
will be supported going forward or was this
should one not unlink() after the close?
When using Mail::Sender only the first email is sent on my mod_perl
server.
When I investigated, I realised that the socket to the SMTP server was
staying open after the completion of that first email (presumably mod_perl
is responsible for this
Ged Haywood wrote:
Hi there,
On Tue, 11 Dec 2001, Jonathan M. Hollin wrote:
When using Mail::Sender only the first email is sent on my mod_perl server.
When I investigated, I realised that the socket to the SMTP server was
staying open after the completion of that first email
: ) No problem, I guess I am unsure if this is the proper way to setup an
Access, Authen, Authz handler. When I use this configuration my 'handler()'
method does not get called and I get an error in the logs:
[Mon Dec 10 13:13:03 2001] [crit] [client 192.168.0.1] configuration error:
couldn't
This is just a reminder that we need your votes. So far we have about
130 votes. Please help us to choose.
Stas Bekman wrote:
Thomas Klausner, Allan Juul and Carlos Ramirez have answered the
challenge and submitted their modperl site designs. Thank you folks!
Now it's a time for you to
Jay Lawrence [EMAIL PROTECTED] said something to this effect on 12/11/2001:
In my development I neglected to supply the Apache request
object when I called Apache::Request-new( $r ). Actually $r
was undef. It still works! I am just wondering if this is
expected behaviour and if it will be
: ) No problem, I guess I am unsure if this is the proper way
to setup an
Access, Authen, Authz handler. When I use this configuration my
'handler()'
method does not get called and I get an error in the logs:
This is *not* the correct way to invoke it.
Directory
for example if the protected url was http://www.site.com/ the user
would be redirected to http://www.site.com/error/401 for the error
message.. and because its protected wouldnt display the custom error
page instead displaying the following error Additionally, a 401
Authorization Required
Actually, I DON'T want the browser to prompt for a username/pass. I saw the
examples in the eagle book and they all seem to use Authz, with Auth
handlers using the example you showed.
Perhaps I need to modify the headers so that the prompt does not occur?
Thanks for the info,
-Original
Hi!
I've got a small CPAN Namespace Question:
Some time ago I wrote CGI::URI2param (
http://search.cpan.org/search?mode=modulequery=URI2param
).
Now, thanks to an idea by darren chamberlain, I wrote a small
PerlInitHandler that does nothing more than parse some PerlSetVars and then
call
With the PerlModule/%INC problem recently being rehashed, here's another one
involving PerlModule vs. use that will really bake your noodle.
Attached is a full mod_perl trace, where I hacked into perl_require_module a
dump of one of my vanishing namespaces on each module load. So you can
Works fantasticaly!
thanks so much.
DJ
- Original Message -
From: Rob Bloodgood [EMAIL PROTECTED]
To: DJ (David J Radunz) [EMAIL PROTECTED]
Cc: mod_perl [EMAIL PROTECTED]
Sent: Wednesday, December 12, 2001 6:09 AM
Subject: RE: anyone know a trick with displaying 401 error messages for
Hi,
I'm using Apache::SizeLimit (on both Solaris and Linux) and getting the
error_log entry:
[Tue Dec 11 15:01:19 2001] (2520) Apache::SizeLimit httpd process too big,
exiting at SIZE=44964 KB SHARE=10900 KB REQUESTS=389 LIFETIME=9505
seconds
But the child process often doesn't exit right
I'm using Apache::SizeLimit (on both Solaris and Linux) and getting the
error_log entry:
[Tue Dec 11 15:01:19 2001] (2520) Apache::SizeLimit httpd process too big,
exiting at SIZE=44964 KB SHARE=10900 KB REQUESTS=389 LIFETIME=9505
seconds
But the child process often doesn't exit right
Can I _upsh_ handlers from within Perl sections? If so, how?
Issac
--
Internet is a wonderful mechanism for making a fool of
yourself in front of a very large audience.
--Anonymous
Moving the mouse won't get you into trouble... Clicking it might.
--Anonymous
PGP Key 0xE0FA561B -
[EMAIL PROTECTED] writes:
I'm using Apache::SizeLimit (on both Solaris and Linux) and getting the
error_log entry:
[Tue Dec 11 15:01:19 2001] (2520) Apache::SizeLimit httpd process too
big,
exiting at SIZE=44964 KB SHARE=10900 KB REQUESTS=389 LIFETIME=9505
seconds
But the child process
IMHO, this looks similar to (though more catastrophic than) the problem I have been
dealing with for some time now.
From the archive :
http://groups.yahoo.com/group/modperl/message/38622
There is a long thread about it. It is presently unresolved. (We're hoping for
Divine intervention.
On December 11, 2001 04:25 pm, Mod_perl Mailing List wrote:
Hi Perrin,
That was it. The child exited immediately when I hit the limit with
KeepAlive Off. Now the question is: Is there a way to force an exit even
with KeepAlive On?
Thanks!
Bob
For what its worth, I'd recommend
Just thought people might be
interested...
I sat down the other day and wrote a test
script to try out various caching implementations. The script is pretty basic at
the moment, I just wanted to get an idea of the performance of different
methods.
The basic scenario is the common mod_perl
All is well until you reach the end,
where it starts reloading everything, and the namespace is
now completely gone.
Are you using PerlFreshRestart?
I posted this once before and got blown off -- a pox
on to those who tell me to check @INC or what not.
No need to get testy. If this is
I sat down the other day and wrote a test script to try
out various caching implementations.
Very interesting. Looks like Cache::Mmap deserves more attention (and
maybe a Cache::Cache subclass).
Have I missed something obvious?
Nothing much, but I'd like to see how these numbers vary with
That was it. The child exited immediately when I hit the limit with
KeepAlive Off. Now the question is: Is there a way to force an exit
even
with KeepAlive On?
As Jay already pointed out, you usually don't want KeepAlive on with
mod_perl. However, you could try changing the call
That was it. The child exited immediately when I hit the limit with
KeepAlive Off. Now the question is: Is there a way to force an exit
even
with KeepAlive On?
As Jay already pointed out, you usually don't want KeepAlive on with
mod_perl. However, you could try changing the call
I'm getting the following error,
$ perl -MApache::Request -e 'Apache::Request-new'
Can't locate object method new via package Apache::Request (perhaps you forgot to
load Apache::Request?) at -e line 1.
$
...both from the command line and under a PerlHandler Apache::Registry'd
script.
Of
Chris Winters wrote:
* Russell Matbouli ([EMAIL PROTECTED]) [011209 19:44]:
As the final year project for my degree, I'm implementing a
user-customisable website application (aimed at multiuser websites)
in mod_perl. Can anyone tell me if something like this already
exists? My searches so far
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On Tue, Dec 11, 2001 at 11:08:07PM -0500, Perrin Harkins wrote:
Are you using PerlFreshRestart?
Same behavior, on or off.
No need to get testy.
That came out wrong, apparently. Sorry.
You should be able to replace a PerlModule call with
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On Tue, Dec 11, 2001 at 05:33:12PM -0800, David Pisoni wrote:
IMHO, this looks similar to (though more catastrophic than) the problem I
have been dealing with for some time now.
From the archive :
On Tue, Dec 11, 2001 at 04:15:49PM -0600, Stephen Clouse wrote:
With the PerlModule/%INC problem recently being rehashed, here's another one
involving PerlModule vs. use that will really bake your noodle.
Attached is a full mod_perl trace, where I hacked into perl_require_module a
dump of
Just wanted to add an extra thought that I
forgot to include in the previous post.
One important aspect missing from my tests
is the actual concurrency testing. In mostreal world programs, multiple
applications will be reading from/writing to the cache at the same time.
Depending on the
One important aspect missing from my tests is the actual concurrency
testing.
Oh, I guess I should have checked your code. I thought these were
concurrent. That makes a huge difference.
2. Lock some part of cache for a request
(Cache::Mmap buckets, MLDBM pages?)
MLDBM::Sync locks the
Hi there,
On Tue, 11 Dec 2001, Titus Brown wrote:
Do you know how I can turn on debugging symbols so that gdb can give me
more info (about line number, etc.)?
I've forced 'gcc' to always have the -g flag on, but that doesn't seem
to be enough for some reason...
The Guide is your friend:
On Tue, 2001-12-11 at 21:00, Stathy Touloumis wrote:
Actually, I DON'T want the browser to prompt for a username/pass. I saw the
examples in the eagle book and they all seem to use Authz, with Auth
handlers using the example you showed.
Perhaps I need to modify the headers so that the prompt
dougm 01/12/11 15:20:34
Modified:src/modules/perl mod_perl.c
Log:
suspend END blocks to be run at server shutdown
Revision ChangesPath
1.99 +7 -0 modperl-2.0/src/modules/perl/mod_perl.c
Index: mod_perl.c
stas01/12/11 21:15:04
Modified:.index.html
Log:
- add a ref to OpenFrame
Revision ChangesPath
1.96 +15 -0 modperl-site/index.html
Index: index.html
===
RCS file:
53 matches
Mail list logo
