mirror of
https://github.com/facebook/sapling.git
synced 2024-10-06 23:07:18 +03:00
3d025d497a
Summary: If a chg server was started by a low priority process, it will inherit the low priority and can be painfully slow. On the other hand, if the chg client was low priority, the user or the automation wants the process to be low priority intentionally. Therefore connecting to an existing chg server might bypass intention. Therefore, detect the low priority case, and refuse to start or connect to a chg server. Previous attempts to workaround slow chg server were removed as they are probably no longer necessary. Reviewed By: singhsrb Differential Revision: D15223518 fbshipit-source-id: 718e807820d481eac204f2293f949c3b315f923d |
||
---|---|---|
.. | ||
chg.1 | ||
chg.c | ||
hgclient.c | ||
hgclient.h | ||
Makefile | ||
procutil.c | ||
procutil.h | ||
README | ||
util.c | ||
util.h |
cHg === A fast client for Mercurial command server running on Unix. Install: $ make $ make install Usage: $ chg help # show help of Mercurial $ alias hg=chg # replace hg command $ chg --kill-chg-daemon # terminate background server Environment variables: Although cHg tries to update environment variables, some of them cannot be changed after spawning the server. The following variables are specially handled: * configuration files are reloaded automatically by default. * CHGHG or HG specifies the path to the hg executable spawned as the background command server. The following variables are available for testing: * 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: 60