Problem with Redis ExpireEntryAt about servicestack HOT 5 CLOSED

Well the redis ExpireAt command takes a Unix time which is in UTC which is what 
the RedisClient sends.

If you're -1hr off your local time, then I'm guessing your servers are located 
in the UK?

It sounds to me that your systems time may not be in sync. I would double check 
that the client and servers are all configured with the correct time and time 
zone.

- Demis

All servers in france, same timezone, i checked this first.
The différence is in fact -2h

Expireat works fine, with a custom convert function.

So you're saying that your own custom function to generate a unixtime works?

This is the source code of the one used in 'redis.ExpireEntryAt':

public const long UnixEpoch = 621355968000000000L;
public static long ToUnixTime(this DateTime dateTime)
{
    var epoch = (dateTime.ToUniversalTime().Ticks - UnixEpoch) / TimeSpan.TicksPerSecond;
    return epoch;
}

I'm guessing your *custom one that works* is similar but without the 
'.ToUniversalTime()'?

I just checked with #redis and they confirm its UTC.

So frances local time now is: 7:00pm
UTC is 5:00pm

Using MONITOR which value gets to redis? 

sorry, your product is ok.
here is my real problem:
http://code.google.com/p/redis/issues/detail?id=318

Sweet, good to know.