Hi there,
On Thu, 28 Jun 2001, Oliver - GoodnGo.COM (R) wrote:
jetzt habe ich tagelang damit zu gebracht den Apache 1.3 zu
installieren und zum Laufen zu bringen ... -
Please post to the mod_perl List in English only.
aber jetzt bekomme ich bei perl Skripten die im cgi-bin Verzeichnis vom
As we see at the list, sometimes users have a problem to start the server
in the 'make test' stage and when they see:
server failed to start! (please examine t/logs/error_log)
many times this log file doesn't exist. So let's check whether the file
exists before we suggest to look at this
On Friday, June 29, 2001, at 07:25 , Shawn Devlin wrote:
What advantages do I gain by grouping the functions based on
functionality? As per my response to Mr. Worrall, one of my concerns
with placing each function call into its own module is the amount of
memory used by the various .pm
memory used by the various .pm files that will be loaded numerous
times. I can see that grouping functions based on functionality would
reduce the number of .pm files in memory. However, if I go that route,
use only loads the .pm once. Multiple uses don't eat up any more resource
than
The minimal-module approach can be managed nicely via Autosplit, which
puts eash sub in its own module with a stub AUTOLOAD that snags things
into core only when they are called
Note that if they do get called this will end up using more memory than if
you had just loaded them during startup,
Note that if they do get called this will end up using more memory than if
you had just loaded them during startup, since they won't be shared between
child processes.
Original assumption is that they are called infrequently. You'll also find
that the amount of memory sucked up by a
