James Cammarata 7ce9968ce1 Properly unlock the socket file lock in ansible-connection (#39223) ... Also use a lock file per host, rather than one global file lock. Commit 9c0275a879 introduced a bug where the lock file was only being unlocked by the child PID of the resulting fork done in ansible-connection. This causes delays when a large inventory causes a lot of contention on that global lock. This patch fixes the problem by ensuring the lock is released regardless of the fork condition, and also to use a lock file based on the remote address of the target host, removing the global lock bottleneck. Fixes #38892		2018-04-25 15:00:15 -05:00
..
ansible	Normalize usage of temp and tmp on tmp (#36221)	2018-02-15 09:01:02 -08:00
ansible-config
ansible-connection	Properly unlock the socket file lock in ansible-connection (#39223)	2018-04-25 15:00:15 -05:00
ansible-console
ansible-doc
ansible-galaxy
ansible-inventory
ansible-playbook
ansible-pull
ansible-vault