[Top][All Lists]
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: [Gnumed-devel] server-client clock mismatches
From: |
Karsten Hilbert |
Subject: |
Re: [Gnumed-devel] server-client clock mismatches |
Date: |
Sat, 10 May 2008 21:00:26 +0200 |
User-agent: |
Mutt/1.5.17+20080114 (2008-01-14) |
On Sat, May 10, 2008 at 07:23:59PM +0200, Karsten Hilbert wrote:
> However, Tobias raised a valid point - while requiring a
> fairly close time sync is all nice and good (for the reasons
> you list below) it can be unhelpful for those poor souls
> running operating systems which make it a hassle to
> atomic-sync their clocks online.
>
> Hence I'll raise the allowance to, say, 5 minutes when
> running in --debug mode while setting it to 1 minute while
> in non --debug mode (which may be some sort of indication of
> "in production"). Now, even in --debug mode the warning will
> appear at > 5 minutes skew but logging in will proceed
> anyways if that's desired.
The code now does this:
- "in production" (== no --debug):
- 1 minute skew allowance
- informs and fails to login on larger skew
- "testing" (== --debug):
- 10 minutes allowance
- warns but allows login to proceed
Hope that makes sense.
10 minutes time-setting accuracy can surely be done manually
on any odd operating system.
Karsten
--
GPG key ID E4071346 @ wwwkeys.pgp.net
E167 67FD A291 2BEA 73BD 4537 78B9 A9F9 E407 1346