Great, thank you guys!
I am trying to first fix my Apache::Session problem before I open
a whole new bag of candy :o)
Thank you very much for your input, I am grateful!
Richard.
- Original Message -
From: "Perrin Harkins" <[EMAIL PROTECTED]>
To: <[EMAIL PROTECTED]>
Cc: <[EMAIL PROTECT
> So by user nobody, you mean in the httpd.conf file in the tags the user and group?
>
> I have it set to user username and group username for each account,
> since all of our boxes use SuExec.
Okay, that may be an issue because SuExec does not work with mod_perl.
Each apache daemon can only run
At 01:25 PM 12/28/2002 -0600, Richard wrote:
>So mod_perl is safe Ok. one other question. If I do upgrade to Mod_Perl,
>can I still run regular Perl scripts, without using Mod_Perl, or do I have
>to use one or the other, only.
Richard,
Yes,you can still run regular cgi, as with MP you have t
So by user nobody, you mean in the httpd.conf file in the I just replied to the PerlMonks reply you did. Thank you.
- Original Message -
From: <[EMAIL PROTECTED]>
To: <[EMAIL PROTECTED]>
Cc: <[EMAIL PROTECTED]>
Sent: Saturday, December 28, 2002 12:08 PM
Subject: Re: Apache::Session::MySQ
> Ah. ok. I don't use Mod_Perl, I hear it is a big security risk, since
> it runs as root. Is this true?
It's not true. The parent process runs as root in order to open port 80,
but that's the same for CGI as well. The child processes that actually
handle requests runs as whatever user you speci
Ah. ok. I don't use Mod_Perl, I hear it is a big security risk, since it
runs as root. Is this true? I love how much faster it is, it's not that much
faster, but enough to make me upgrade all my boxes if it is not a security
risk.
What do you think?
Thanks,
Richard.
(I'll go see your reply in a m
> Is this the correct list for help with Apache::Session::MySQL?
This is a good list for it if you are using mod_perl. If you're using
CGI, try one of the CGI resources instead, or stick with perlmonks.org. I
just replied to your post there a few minutes ago.
- Perrin
Is this the correct list for help with
Apache::Session::MySQL?
Thanks,
Richard.
> How did this happen? Why does my command line perl use i386-linux,
> while my mod_perl uses i686-linux?
Simple: they are compiled to use different installations of Perl. If you
want to unify them, you can find out what mod_perl is using and put it
first in your path (so that "perl" will run it)
When I use perl from the command line, my @INC is this:
$ perl -e"print join(':', @INC)"
/usr/lib/perl5/5.6.1/i386-linux:/usr/lib/perl5/5.6.1:/usr/lib/perl5/site_perl/5.6.1/i386-linux:/usr/lib/perl5/site_perl/5.6.1:/usr/lib/perl5/site_perl/5.6.0:/usr/lib/perl5/site_perl:.
When I print @INC from a
> Michael wrote:
> > Hi all.
> >
> > As suggested by Geoff and Stas, I am trying out modperl2.. Now I have
> > some questions:
> >
> > i) with Apache::CommandServer (can be found at
> >
http://perl.apache.org/docs/2.0/user/overview/overview.html#toc_Protocol_Mod
ules_with_mod_perl_2_0),
> > I set
11 matches
Mail list logo