Hi Peter, The CR released version you mentioned is for version 5.3p1-94. I Just did a quick google search and I believe you need a version 5.6 or better to get ControlPersist, unless RedHat backports the feature. The 94 at the end of the version suggests package has been modified at least 93 times since initial packaging -- tweaks, fixes, and backports from RedHat. Looking at the changelog for the source RPM
http://rpm.pbone.net/index.php3/stat/22/idpl/24668559/com/changelog.html and I cant see any evidence of the ControlPersist feature being backported. Kahlil (Kal) Hodgson GPG: C9A02289 Head of Technology (m) +61 (0) 4 2573 0382 DealMax Pty Ltd (w) +61 (0) 3 9008 5281 Suite 1415 401 Docklands Drive Docklands VIC 3008 Australia "All parts should go together without forcing. You must remember that the parts you are reassembling were disassembled by you. Therefore, if you can't get them together again, there must be a reason. By all means, do not use a hammer." -- IBM maintenance manual, 1925 On Thu, Jan 16, 2014 at 6:43 AM, Peter Gehres <[email protected]>wrote: > We have the same problem with CentOS and old openssh. > > I found a new version [1] the other day and plan on trying it out, but > haven't had the chance yet. It is from the CentOS CR (continuous release) > repo [2]. > > [1] - http://lists.centos.org/pipermail/centos > -cr-announce/2013-November/001033.html > [2] - http://wiki.centos.org/AdditionalResources/Repositories/CR > > > On Wed, Jan 15, 2014 at 11:00 AM, Stan Lemon <[email protected]> wrote: > >> This is sort of picking up on an exchange I started with Michael on >> twitter. >> >> I read http://blog.ansibleworks.com/author/michaeldehaan/ and was >> curious about the paramiko piece, specifically if this could be >> circumvented by finding a repo that would server up a newer version of the >> ssh client for me. >> >> I'm also just curious in general what is recommended for using ansible >> both on the host and destination side. I find myself using the latest >> CentOS6 a lot, but wonder if there's a better route I should be looking at >> to ensure speed and efficiency when be managed by ansible. >> >> Thanks, >> >> - Stan Lemon >> [email protected] >> >> -- >> You received this message because you are subscribed to the Google Groups >> "Ansible Project" group. >> To unsubscribe from this group and stop receiving emails from it, send an >> email to [email protected]. >> To post to this group, send email to [email protected]. >> For more options, visit https://groups.google.com/groups/opt_out. >> > > > > -- > Peter Gehres > Site Reliability Engineer | AppDynamics, Inc. > www.appdynamics.com | AS62897 > > -- > You received this message because you are subscribed to the Google Groups > "Ansible Project" group. > To unsubscribe from this group and stop receiving emails from it, send an > email to [email protected]. > To post to this group, send email to [email protected]. > For more options, visit https://groups.google.com/groups/opt_out. > -- You received this message because you are subscribed to the Google Groups "Ansible Project" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To post to this group, send email to [email protected]. For more options, visit https://groups.google.com/groups/opt_out.
