expiration of lock_key should be relative

[crhg]

Memcached uses monotonic clock if available, and it differs from the clock outside of it. The difference may be very large when memcached is running long time. In such cases, specifying expiration time as absolute time does not work as expected.

For example, the clock of our memcached running about 2 years are about 1 hour ahead. As a result, session lock does not work properly because expire parameter of lock (= time() + max_execution_time(30s) + 1) is past from the point of view of memcached, and therefore the lock expires immediately.

This problem can be avoided by specifying expiration parameter as number of seconds starting from current time, not absolute Unix time.

[mkoppanen]

Makes sense. Can you open a PR for this?

[crhg]

It is difficult for me because I'm not familiar with github.

[mkoppanen]

Ok, I'll fix this today. Thanks for the report!

[johnwho]

Does anyone have a patch for this?
I'll need it before long because my memcached is running for over a year.

[mkoppanen]

See #149

[johnwho]

Thanks.