Message-ID: <517A7144.4070204@xk7.net>
Date: Fri, 26 Apr 2013 13:21:24 +0100
From: Paul Waring <paul@xk7.net>
User-Agent: Mozilla/5.0 (X11; Linux x86_64;
	rv:17.0) Gecko/20130329 Thunderbird/17.0.5
MIME-Version: 1.0
To: pgsql-www@postgresql.org
Subject: Re: Can we change auto-logout timing on wiki.postgresql.org?
References: <5179CD76.6030908@agliodbs.com>
	<CABUevEymuYyyof68ASuDt9GBpFOvF2r0WNyk8JxK1nbGG70Rpw@mail.gmail.com>
	<517A6C78.7000101@xk7.net>
	<CABUevEw0asBAR6jS=aqKBG1OAJmTsMP1FiocCm-cLJfqGEAm_w@mail.gmail.com>
In-Reply-To: 
 <CABUevEw0asBAR6jS=aqKBG1OAJmTsMP1FiocCm-cLJfqGEAm_w@mail.gmail.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Precedence: bulk
Sender: pgsql-www-owner@postgresql.org

On 26/04/13 13:06, Magnus Hagander wrote:
>> As far as I can tell from examining the headers, it looks like an expiry
>> date/time is set for the login cookie, but then it is never updated. If this
>> is the case, then eventually the expiry date will pass and the browser will
>> delete the cookie, even if you have been regularly accessing the wiki.
>>
>> Another possibility is that the cronjob which auto-removes session files
>> (assuming files are being used) is set to the default of 24 minutes - which
>> will remove your session after that time regardless of what the cookie's
>> expiry date is set to.
>
> We do have session.gc_maxlifetime set to 1440 which is the 24 minutes
> you're referring to? So maybe this is the parameter we need to
> (drastically) increase?

Assuming session data is being stored in files (you can check that with 
session.save_handler), then you might want to increase 
session.gc_maxlifetime.

The cleanup cronjob runs at 9 and 39 minutes past the hour by default, 
so a session file might be deleted 24-54 minutes since it was last modified.

-- 
Paul Waring
http://www.pwaring.com


-- 
Sent via pgsql-www mailing list (pgsql-www@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-www