# HG changeset patch
# User Jun Wu <quark@fb.com>
# Date 1466022991 -3600
# Node ID 66d41c9e92220e4dbbe14943edf70aa231e56ef8
# Parent  93b83ef78d1e8c285fad367899bbff46949317ba
chg: change default connect timeout to 60 seconds

As discussed at
https://www.mercurial-scm.org/pipermail/mercurial-devel/2016-June/085290.html

The default 10-second timeout is not enough if the machine is overloaded.
Let's increase it to 60 seconds.

diff -r 93b83ef78d1e -r 66d41c9e9222 contrib/chg/README
--- a/contrib/chg/README	Tue Jun 14 18:14:42 2016 -0700
+++ b/contrib/chg/README	Wed Jun 15 21:36:31 2016 +0100
@@ -29,4 +29,4 @@
  * CHGDEBUG enables debug messages.
  * CHGSOCKNAME specifies the socket path of the background cmdserver.
  * CHGTIMEOUT specifies how many seconds chg will wait before giving up
-   connecting to a cmdserver. If it is 0, chg will wait forever. Default: 10
+   connecting to a cmdserver. If it is 0, chg will wait forever. Default: 60
diff -r 93b83ef78d1e -r 66d41c9e9222 contrib/chg/chg.c
--- a/contrib/chg/chg.c	Tue Jun 14 18:14:42 2016 -0700
+++ b/contrib/chg/chg.c	Wed Jun 15 21:36:31 2016 +0100
@@ -250,7 +250,7 @@
 
 	debugmsg("try connect to %s repeatedly", opts->sockname);
 
-	unsigned int timeoutsec = 10;  /* default: 10 seconds */
+	unsigned int timeoutsec = 60;  /* default: 60 seconds */
 	const char *timeoutenv = getenv("CHGTIMEOUT");
 	if (timeoutenv)
 		sscanf(timeoutenv, "%u", &timeoutsec);