ansible/changelogs/fragments/persistent-socket-lock-name.yaml

---
bugfixes:
- Changes how ansible-connection names socket lock files. They now use
  the same name as the socket itself, and as such do not lock other
  attempts on connections to the same host, or cause issues with
  overly-long hostnames.
[2.7] Don't fail if a remote_addr with a '/' hits ansible_connection (#49781) (#50037) * [2.7] Don't fail if a remote_addr with a '/' hits ansible_connection (#49781) * Fail if a remote_addr with a '/' hist ansible_connection This is _probably_ a CIDR block, but anything with a slash will fail, so no need to try to parse to make sure * Locks are now per-socket_path. Locks use the same value as socket_path. Locks are also cleaned up in shutdown like sockets. (cherry picked from commit 61a649c) Co-authored-by: Nathaniel Case <this.is@nathanielca.se> * Add changelog 2019-01-07 18:32:55 +01:00			`---`
			`bugfixes:`
			`- Changes how ansible-connection names socket lock files. They now use`
			`the same name as the socket itself, and as such do not lock other`
			`attempts on connections to the same host, or cause issues with`
			`overly-long hostnames.`