1. 08 Sep, 2015 16 commits
  2. 07 Sep, 2015 2 commits
  3. 06 Sep, 2015 1 commit
  4. 05 Sep, 2015 3 commits
  5. 04 Sep, 2015 16 commits
  6. 03 Sep, 2015 2 commits
    • Go back to using ~/.ansible/cp as the ControlPath · 7aa6cd3f
      This was commented out earlier because of the lack of interprocess
      locking and prepare_writeable_dir in v2.
      
      The locking was not needed: it could only protect against other siblings
      of this process (since they were all locking a temporary file that was
      opened in the parent), and those would be running as the same user and
      with the same umask. Also, os.makedirs() tolerates intermediate paths
      being created by other processes. For any other kind of error, both
      locking and non-locking code paths would fail in the same way.
      
      So all we really need to do is make sure we have write permissions.
      
      (We also move the cp_dir handling code to where we actually set the
      ControlPath ourselves; if the user has set it via ssh_*args already,
      we don't need to bother.)
      Abhijit Menon-Sen committed