Dan McCormick wrote:
Hi,
I'm running a site with Apache, MySQL, Mason, and
Apache::Session::MySQL. I've been sporadically seeing this message in
my error log:
[Wed Jul 9 20:41:42 2003] [error] Magic number checking on storable
string failed at blib/lib/Storable.pm (autosplit into
blib/lib/auto
--- Perrin Harkins [EMAIL PROTECTED] wrote:
If you look at the actual contents of
Apache::Session::MySQL, you'll see
that it's essentially just a config file. There's
no need to be
concerned about using Flex, but you could easilly
code up your own
Apache::Session::MySQLNoLocks
--- md [EMAIL PROTECTED] wrote:
Is it possible to have row-level locking (as opposed
to table-level or null locker) with MySQL 4.x and
Apache::Session?
Looks like I get that with InnoDB automatically...
__
Do you Yahoo!?
Yahoo! Tax Center -
md wrote:
--- md [EMAIL PROTECTED] wrote:
Is it possible to have row-level locking (as opposed
to table-level or null locker) with MySQL 4.x and
Apache::Session?
You effectively have that already, since the MySQL locker only locks an
individual session. Check the code.
Looks like I get that
We're using Apache::Session::MySQL (Apache::Session
1.54) and occassionaly see long lock times.
Also, we'll soon be adding a substantial number of
users to our system and I wonder if it would be wise
to move away from the table locking that is currently
being used with Apache::Session::MySQL
On Tuesday, February 25, 2003, at 11:55 AM, md wrote:
We're using Apache::Session::MySQL (Apache::Session
1.54) and occassionaly see long lock times.
I had a similar problem a few months ago with
Apache::Session::Postgres. I occasionally had Apache processes hang,
and a quick ps aux shows
md wrote:
Also, we'll soon be adding a substantial number of
users to our system and I wonder if it would be wise
to move away from the table locking that is currently
being used with Apache::Session::MySQL.
It would be. Frankly, there is no value to the kind of mutual exclusion
that the Apache
be able to
remove someday:)...but never-the-less, very little
data in the session. I've gotten most of my sessioning
information from this list (and you), so I believe we
are session correctly :)
If you look at the actual contents of
Apache::Session::MySQL, you'll see
that it's essentially just
Is this the correct list for help with
Apache::Session::MySQL?
Thanks,
Richard.
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
in a min. Thank you!)
- Original Message -
From: [EMAIL PROTECTED]
To: [EMAIL PROTECTED]
Cc: [EMAIL PROTECTED]
Sent: Saturday, December 28, 2002 11:49 AM
Subject: Re: Apache::Session::MySQL
Is this the correct list for help with Apache::Session::MySQL?
This is a good list for it if you
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
12:08 PM
Subject: Re: Apache::Session::MySQL
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
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 to
So by user nobody, you mean in the httpd.conf file in the virtualhost
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
]
Sent: Saturday, December 28, 2002 2:32 PM
Subject: Re: Apache::Session::MySQL
So by user nobody, you mean in the httpd.conf file in the virtualhost
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
On Mon, 18 Dec 2000, Andreas Marienborg wrote:
I just can't seem to find any info on how to specify that Apache::Session
should create session_id's that are shorter than 32 hex chars? could
someone point me in the right direction??
You can use the argument 'IDLength' when using
I just can't seem to find any info on how to specify that Apache::Session
should create session_id's that are shorter than 32 hex chars? could
someone point me in the right direction??
thanks in advance
Andreas
--
Andreas Marienborg +47 92 28 63 82
[EMAIL PROTECTED]
. Apache::Session::MySQL is
remarkably simple. Here it is:
package Apache::Session::MySQL;
use strict;
use vars qw(@ISA $VERSION);
$VERSION = '1.01';
@ISA = qw(Apache::Session);
use Apache::Session;
use Apache::Session::Lock::MySQL;
use Apache::Session::Store::MySQL;
use Apache::Session
write a module to sub class Apache::Session. Apache::Session::MySQL is
remarkably simple. Here it is:
Thanks for pointing this out..however, I found a better way I thought I'd
share with the list:
The Apache::Session::Generate::MD5 module actually checks if there is an
arg called 'IDLength
CGI
#PerlInitHandler Apache::StatINC
#PerlSetVar StatINCDebug On
PerlModule Apache::DBI
/Files
sample.cgi --
use strict;
use Apache;
use Apache::Session::MySQL;
use CGI;
use CGI::Cookie;
my $q = new CGI;
my %session;
eval {
my $r = Apache-request;
my %cookie = CGI::Cookie-parse($r-header_i
Thu, 20 Jul 2000 14:29:40 -0700 (PDT)
"Jeffrey W. Baker" [EMAIL PROTECTED] wrote:
The problem is, if an acquired Session ID (from Cookie)
is not stored in the session database, Apache goes like
panic: POPSTACK
Callback called exit.
I know Apache::Session will die "Object does
22 matches
Mail list logo
