On Sun, April 29, 2007 11:50 pm, Aaron Axelsen wrote:
> I did some more investigating, and tracked down the problem.
> Apparently, even though i was setting a separate save_path inside the
> default save path the garbage collector was still picking up the
> sessions in that directory.
>
> I moved t
I did some more investigating, and tracked down the problem.
Apparently, even though i was setting a separate save_path inside the
default save path the garbage collector was still picking up the
sessions in that directory.
I moved the session save_path dir to a separate location and the
sessions
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Everything i've read in the documentation states to call session_start
after you have changed your necessary settings. Do you have a working
example using session cookies I can compare this with?
Richard Lynch wrote:
> On Fri, April 27, 2007 1:37 pm
On Fri, April 27, 2007 1:37 pm, tedd wrote:
> At 12:26 PM -0500 4/27/07, Aaron Axelsen wrote:
>>With the following set, its still timing me out. I logged in and
>>waited about 40 minutes, and it was timed out by then. This is
>>getting very confusing, what else could it be that is causing this to
On Fri, April 27, 2007 12:26 pm, Aaron Axelsen wrote:
> With the following set, its still timing me out. I logged in and
> waited about 40 minutes, and it was timed out by then. This is
> getting very confusing, what else could it be that is causing this to
> not work?
The usual suspcect is that
On 4/27/07, tedd <[EMAIL PROTECTED]> wrote:
At 12:26 PM -0500 4/27/07, Aaron Axelsen wrote:
>With the following set, its still timing me out. I logged in and
>waited about 40 minutes, and it was timed out by then. This is
>getting very confusing, what else could it be that is causing this to
>n
At 12:26 PM -0500 4/27/07, Aaron Axelsen wrote:
With the following set, its still timing me out. I logged in and
waited about 40 minutes, and it was timed out by then. This is
getting very confusing, what else could it be that is causing this to
not work?
session_name('myapp');
$mytimeout = 1
With the following set, its still timing me out. I logged in and
waited about 40 minutes, and it was timed out by then. This is
getting very confusing, what else could it be that is causing this to
not work?
session_name('myapp');
$mytimeout = 180 * 60; // minutes * 60
session_set_cookie_param
I now have the following settings:
session_name('myapp');
$mytimeout = 180 * 60; // minutes * 60
session_set_cookie_params($mytimeout);
$sessdir = ini_get('session.save_path')."/myapp";
if (!is_dir($sessdir)) { mkdir($sessdir, 0777); }
ini_set('session.save_path', $sessdir);
// New Attempt
sess
On 4/27/07, Aaron Axelsen <[EMAIL PROTECTED]> wrote:
I now have the following settings:
session_name('myapp');
$mytimeout = 180 * 60; // minutes * 60
session_set_cookie_params($mytimeout);
$sessdir = ini_get('session.save_path')."/myapp";
if (!is_dir($sessdir)) { mkdir($sessdir, 0777); }
ini_s
On 4/27/07, Aaron Axelsen <[EMAIL PROTECTED]> wrote:
I am trying to change my session timeout to 180 minutes, and everything
ive tried has not worked. Does anyone have any idea why this isn't
working properly?
I currently am trying to set the following:
session_name('myapp');
$mytimeout = 180
I am trying to change my session timeout to 180 minutes, and everything
ive tried has not worked. Does anyone have any idea why this isn't
working properly?
I currently am trying to set the following:
session_name('myapp');
$mytimeout = 180 * 60; // minutes * 60
session_set_cookie_params($myti
12 matches
Mail list logo
