Log timestamps lag behind after a laptop suspend

I use my laptop for developing to-be-production CB-based software. If I suspend and later wake it up, the timestamps in the log files (e.g. /opt/couchbase/var/lib/couchbase/logs/couchdb.log) will lag behind by the amount my laptop spent suspended.

E.g. if I suspend it for 10 hours overnight, records logged at 2014-10-15T09:00:00 will have the timestamp 2014-10-14T23:00:00 or so. This makes timestamps in the log files effectively useless.

Expected behavior: all the timestamps should reflect the actual time at that point, as correctly known by the operating system, and as returned by the time()/gettimeofday()/localtime()/strftime()/etc. kernel/glibc calls.

(BTW this bug also makes me wonder whether DST changes are handled correctly. I haven't tested that.)