I keep a unique 'filestamp' in the database under each customer-- a 32-digit
randomly-generated number that then can be used either as a part of image
filenames, or as a directory name which contains a customer's images.
That way, in order for one customer to see another's images, they'd
On Sun, 24 Jun 2001, Stas Bekman wrote:
On Sun, 24 Jun 2001, Brooklyn Linux Solutions CEO wrote:
It's got to be built in. My mod_perl conf keeps looking in 5.6.0 in the @INC
array even after the 5.6.1 upgrade
I got sick of the problem and linked 5.6.1 into 5.6.0
You could
On Mon, 25 Jun 2001, Stas Bekman wrote:
On Sun, 24 Jun 2001, Todd Goldenbaum wrote:
On Sun, 24 Jun 2001, Stas Bekman wrote:
On Sun, 24 Jun 2001, Brooklyn Linux Solutions CEO wrote:
It's got to be built in. My mod_perl conf keeps looking in 5.6.0 in the
@INC
array even
Thanks Andrew- good stuff. You've convinced me, I'm just going to bite the
bullet and rebuild :)
todd
On Sun, 24 Jun 2001, Andrew Ho wrote:
Todd,
Perl and mod_perl are separate entities altogether. Perl is the scripting
language. mod_perl is an extension to Apache, which builds a Perl
actually using 5.006!
So far as I can tell, I don't even have a copy of perl 5.006 on my system...
Is mod_perl actulaly distributed with a version of perl interpreter intact?
If so, How do I upgrade it?
thanks,
Todd Goldenbaum
[EMAIL PROTECTED]
On Sat, 23 Jun 2001, Steven Lembark wrote:
I am running Apache/1.3.14 (Unix) mod_perl/1.25 on a redhat 7 system.
Since the perl binary that came with the redhat distribution was version
5.6.0, I assumed that is the version that got built into mod perl
(statically linked). But I just
On Sat, 23 Jun 2001, Chris Reinhardt wrote:
On Sat, 23 Jun 2001, Todd Goldenbaum wrote:
Hi,
I am running Apache/1.3.14 (Unix) mod_perl/1.25 on a redhat 7 system.
Since the perl binary that came with the redhat distribution was
version 5.6.0, I assumed that is the version that got
