Managed to get my login time out set to 1 sec. Is the Admin preferences saved in the database or a file.
Greetings, On 12-10-13 16:23, Jack Morash wrote:
Managed to get my login time out set to 1 sec. Is the Admin preferences saved in the database or a file.
Might be worth filing a bug, we should perhaps ensure that that can't be set to something unreasonable, e.g. < 60 seconds.
+1 to that idea. A little bit of lag, and *BOOM* a 1 second timeout fails to log a user in. That is unacceptable to the average user, because they'll keep trying and trying and trying only become more and more frustrated with the system. As for what a reasonable time out is, I think 60 seconds is a good overall number, but perhaps something as low as 30 seconds might be okay. Anything lower is tempting fate. I'll admit to a 20 second timeout, but since I have a multi-key solution (20 seconds per key) in my specialized login code, that gives me 40 seconds overall. GPML, Mark Tompsett
On 13 October 2013 13:16, Mark Tompsett <mtompset@hotmail.com> wrote:
Greetings,
On 12-10-13 16:23, Jack Morash wrote:
Managed to get my login time out set to 1 sec. Is the Admin preferences saved in the database or a file.
Might be worth filing a bug, we should perhaps ensure that that can't be set to something unreasonable, e.g. < 60 seconds.
+1 to that idea. A little bit of lag, and *BOOM* a 1 second timeout fails to log a user in. That is unacceptable to the average user, because they'll keep trying and trying and trying only become more and more frustrated with the system.
As for what a reasonable time out is, I think 60 seconds is a good overall number, but perhaps something as low as 30 seconds might be okay. Anything lower is tempting fate. I'll admit to a 20 second timeout, but since I have a multi-key solution (20 seconds per key) in my specialized login code, that gives me 40 seconds overall.
Hi Mark You've misunderstood, this is the inactivity timeout, there is no timeout for completing a login request. What has happened is the person has the set the inactivity timeout for 1second, which doesn't give them enough time to get to systempreferences and change it back. It times them out 1 second after they login. However Robin is right, not allowing the inactivity timeout to be set for less than a minute is probably a good idea. Chris
Hi, On Sun, Oct 13, 2013 at 5:51 AM, Chris Cormack <chris@bigballofwax.co.nz> wrote:
On 13 October 2013 13:16, Mark Tompsett <mtompset@hotmail.com> wrote:
Greetings,
On 12-10-13 16:23, Jack Morash wrote: <snipped>
However Robin is right, not allowing the inactivity timeout to be set for less than a minute is probably a good idea.
+1 When accessing an Koha instance over GPRS / Edge using a GSM / CDMA usb modem over weak signal coverage area, anything less would result in a time out. Even 60 sec may be on the shorter side -- Indranil Das Gupta Phone : +91-98300-20971 Blog : http://indradg.randomink.org/blog IRC : indradg on irc://irc.freenode.net Twitter : indradg -=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-==-=-=-=-=-=-=-=-=- Please exchange editable Office documents only in ODF Format. No other format is acceptable. Support Open Standards. For a free editor supporting ODF, please visit LibreOffice - http://www.documentfoundation.org
participants (5)
-
Chris Cormack -
Indranil Das Gupta -
Jack Morash -
Mark Tompsett -
Robin Sheat