James Cammarata 4d0422d4ed Properly unlock the socket file lock in ansible-connection (#39223) (#39330) ... 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 (cherry picked from commit 7ce9968ce1)		2018-05-01 14:19:26 -07:00
..
ansible	Normalize usage of temp and tmp on tmp (#36221)	2018-02-15 09:01:33 -08:00
ansible-config	1st part of ansible config, adds ansible-config to view/manage configs (#12797)	2017-06-14 11:08:34 -04:00
ansible-connection	Properly unlock the socket file lock in ansible-connection (#39223) (#39330)	2018-05-01 14:19:26 -07:00
ansible-console
ansible-doc
ansible-galaxy
ansible-inventory	ansible-inventory cli tool (#22477)	2017-08-15 16:45:54 -04:00
ansible-playbook
ansible-pull
ansible-vault