[
https://issues.apache.org/jira/browse/COUCHDB-204?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12715223#action_12715223
]
Damien Katz commented on COUCHDB-204:
-------------------------------------
It looks like all we need is a special flag passed to the emulator
http://www.erlang.org/doc/man/erl.html:
+c
Disable compensation for sudden changes of system time.
Normally, erlang:now/0 will not immediately reflect sudden changes in the
system time, in order to keep timers (including receive-after) working.
Instead, the time maintained by erlang:now/0 is slowly adjusted towards the new
system time. (Slowly means in one percent adjustments; if the time is off by
one minute, the time will be adjusted in 100 minutes.)
When the +c option is given, this slow adjustment will not take place. Instead
erlang:now/0 will always reflect the current system time. Note that timers are
based on erlang:now/0. If the system time jumps, timers then time out at the
wrong time.
> CouchDB stops/crashes/hangs (?) after resume from Mac OS X system hibernation
> and/or stand-by ("sleep")
> -------------------------------------------------------------------------------------------------------
>
> Key: COUCHDB-204
> URL: https://issues.apache.org/jira/browse/COUCHDB-204
> Project: CouchDB
> Issue Type: Bug
> Components: Administration Console, Database Core, HTTP Interface,
> Infrastructure
> Affects Versions: 0.8.1
> Environment: Mac OS X 10.5.6 "Leopard"
> Reporter: Philipp Schumann
> Priority: Critical
>
> I'm running CouchDB 0.8.1 on Mac OS X 10.5.6 "Leopard" and after resuming
> from system hibernation ("safe sleep" -- by closing and reopening the laptop
> lid in my case, which is the factory default), the process either refuses all
> incoming connections, including my own Python scripts, web browser and the
> Futon, or has stopped running altogether. That is, I don't know which exactly
> is the case here but the fact is that CouchDB cannot be connected to after
> resuming.
> This issue always appears with "smart sleep / safe sleep" (standby plus
> hibernation) but only sometimes appears using "fast sleep" (hibernation
> turned off, standby only).
> This isn't a "critical" issue for server deployments, of course, but one of
> the core ideas of CouchDB is that eventually it will be deployed even to
> desktop clients for app & data replication across machines, so in this
> context this *is* a critical issue since you can't ask "ordinary" Mac OS X
> users to change their sleep settings from "safe" to "fast" using
> uncomprehensable terminal commands.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
