This is just a pre-announce...
The short story:
We need somebody to do the coordination for the modperl banners project,
similar to what Jonathan has done with the new logo creation/selection
project.
The long story:
We need to create a few banners, so we can use these as ads on friendly
Hi
winnt/as561/ modperl 1_26_01-dev / apache 1.3.22
I installed Apache::DB module from theoryx5 repository.
I put the necessary directives in httpd.conf.
It is said to start apache with -X flag. but there is no such
possibility on win32 apache. so i started the server normally
and manually in
Is the webserver useful if you have an error that warrants sending a
mail? If sending an email means the server is broken having a flood of
mails may be a feature. It will be incentive to fix whatever is
breaking your server/db.
Also, I would strongly recommend keeping your warning system as
Benjamin Elbirt wrote:
Well, lets assume that I were to go with
the shared memory option anyway... what would the pitfalls be / concerns?
As mentioned before, you'd probably be better off with MLDBM::Sync or
Cache::Cache. You can try IPC::Shareable, but a lot of people seem to
have trouble
To all who may help,
I have a few Perl scripts that updates our Novell Directory using the
Net::LDAP module. My question is I have created a ldap properties file that
has the bind user and a few other items like scope and base. I would like
to know the best way to secure this file but still
Cox, Todd (NCI) [EMAIL PROTECTED] writes:
I have a few Perl scripts that updates our Novell Directory using the
Net::LDAP module. My question is I have created a ldap properties file that
has the bind user and a few other items like scope and base. I would like
to know the best way to
On Wed, 17 Apr 2002, Perrin Harkins wrote:
Benjamin Elbirt wrote:
Well, lets assume that I were to go with
the shared memory option anyway... what would the pitfalls be / concerns?
As mentioned before, you'd probably be better off with MLDBM::Sync or
Cache::Cache. You can try
I am desperate enough to use this thread to try to get an answer to my own
IPC question. ;)
I keep getting the following error using OPEN3 along with the appropriate
modifications to my code for using mod_perl with Perl 5.6.1. The offending
(and it is very offensive to me!) is:
[error] open3:
I'm using AuthCookie and as some of you know, if it determines your
session to be invalid it redirects to a login page instead by way of a
FORBIDDEN response coupled with a custom error page.
My app has a frameset (navigation on the left, and two data frames on
the right). I know the evils
In httpd.conf i have
Location /~jter
PerlAccessHandler ApacheAuthentication
PerlSetVar Intranet 65.103.229.188 = joe, 10.10.10.2 = userB
PerlAuthenHandler ApacheAuthentication
AuthName realm
AuthType Basic
Require valid-user
Order deny,allow
On Tue, Apr 16, 2002 at 06:05:11PM -0400, Sam Tregar wrote:
On Tue, 16 Apr 2002, Sam Tregar wrote:
On 16 Apr 2002, Garth Winter Webb wrote:
Sam, try getting rid of the 'PerlModule Apache::DB' line. I've used
Apache::DProf w/o any problems by including only the one PerlModule
These are the software/platform I'm working with:
Solaris 8
Perl 5.6.1
OpenSSl-0.9.6c
mod_ssl-2.8.8-1.3.24
mod_perl-1.24_01
Apache 1.3.24
These are the steps that I've taken to install the modules:
Installing OpenSSl :
Abstracting access to data is only half of the storythe more challenging
part is race conditions and lock management...
Perrin Harkins wrote:
Stas Bekman wrote:
You cannot do that unless you use IPC, which is usually only useful if
he variable is small. DBM file is another solution if
Unfortunately everyone wants to use email for everything.the proper
way would
be to use some facilities that have proven track record, like syslogd(1d)
on each
box. As you know syslogd() allows you to route a message to a remote
box. So,
you assign one of your boxes as the final or central
Abstracting access to data is only half of the storythe more
challenging
part is race conditions and lock management...
All of the data sharing tools take the logistics of multi-process
read/write situations into account, although they do it in different
ways. Some use file locking,
Fernando Munoz wrote:
These are the software/platform I'm working with:
Solaris 8
Perl 5.6.1
OpenSSl-0.9.6c
mod_ssl-2.8.8-1.3.24
mod_perl-1.24_01
Apache 1.3.24
These are the steps that I've taken to install the modules:
Try to follow
Is mod_perl supposed to be the final choice of the name ? Someones
suggested before to use a different name like Tomcat for Java. What is the
latest conclusion ?
Peter Bi
- Original Message -
From: Stas Bekman [EMAIL PROTECTED]
To: [EMAIL PROTECTED]
Sent: Tuesday, April 16, 2002 11:54
Thanx Doug for the reply. Unfortunately I still get
segfaults :-( No difference.
Once I have the time, I'll get the stacktrace see
for any clues. Right now I have kept DSO in the
backburner, as I have got PerlFreshRestart fully up
and runnig (with a no. of patches to mod_perl)
Sreeji
--- Doug
Peter Bi wrote:
Is mod_perl supposed to be the final choice of the name ? Someones
suggested before to use a different name like Tomcat for Java. What is the
latest conclusion ?
Where have you been all this time, it was cast in stone already:
http://apache.org/~stas/boulder.gif
:)
Fran:
You may need to 1) add a few lines of code in AuthCookie to make your error
code aware to other methods, and 2) have a dynamic login page that can
interpret the code. Alternatively, you may try AccessCookie I posted. :-)
In AccessCookie, you simply return $error from authenticate(), let
20 matches
Mail list logo
