similar to: Updated ssh-agent authentication retry patch available

This patch updates the files under popt/ to the latest vendor drop. The only change is the inclusion of a FreeBSD-specific patch to popt.c. This is needed in case somebody decides to build rsync on that platform without using the port. I'm not happy about the wording in popt/README.rsync so I may change it. The patch is available at http://www.catnook.com/rsync-popt-1.5.1.patch Comments

--On Monday, May 14, 2007 9:16 PM -0700 Jos Backus <jos@catnook.com> wrote: > ObPuppet: we ramping up our deployment this week to around 200 hosts. So > far everything has been going smoothly. We don''t have nearly as many and yet, we see occasional errors ("End of file reached") which seems to indicate the network cutting out. I can''t imagine what would

Quick and dirty: --- lib/facter.rb (revision 203) +++ lib/facter.rb (working copy) @@ -989,6 +989,18 @@ %x{/usr/sbin/scutil --get LocalHostName} end end + Facter.add(:interfaces) do + confine :kernel => :linux + setcode do + %x{/sbin/ifconfig -a -s}.split($/)[1..-1].collect {|line|

Perhaps now is a good time to commit this patch which updates the included popt to version 1.7. This has been tested on FreeBSD and Solaris. http://www.catnook.com/patches/rsync-popt-1.7.diff Comments? -- Jos Backus _/ _/_/_/ Sunnyvale, CA _/ _/ _/ _/ _/_/_/ _/ _/ _/

http://www.catnook.com/patches/rsync-popt-1.6.4.patch has a patch which upgrades the popt included with rsync to the latest version, 1.6.4. The configure script had to be regenerated (with autoconf 2.53) because popt.c wants HAVE_FLOAT_H. As an aside, I have heard people complain about this version of autoconf generating scripts that break when run under bash (as /bin/sh). Comments? -- Jos

Is there a way to specify on a per-object basis that Puppet should merely report that an object needs to be updated without actually performing the update? This would make it possible to detect changes to critical objects (e.g. config files) that Puppet shouldn''t try to fix automaticaly. -- Jos Backus jos at catnook.com

FYI: We have a custom `checkout'' type which stopped working when migrating from 0.22.4 to 0.23.2-ish. This turned out to have been caused by the location of property.rb changing between 0.22.4 (puppet/type/property.rb) and 0.23.2-ish (puppet/property.rb). (I say 0.23.2-is because I''m using 40491ebe7ca9692b57fb533412ece8fb694b7d4c since it only has a few extra bugfixes over

And lsof the agent too - see what files it has open... Nico -- > -----Original Message----- > From: Kevin Steves [mailto:kevin at atomicgears.com] > Sent: Friday, August 23, 2002 4:48 PM > To: openssh-unix-dev at mindrot.org > Cc: stevesk at pobox.com > Subject: Re: 3.4p1 ssh-agent auth-retry patch available: was: Re: > Updated ssh-agent authentication retry patch available

[Apologies if this is an off-topic question; please direct me to a more appropriate place if so.] Using Kerberos/GSSAPIAuthentication, is there a way to centrally control/manage (perhaps using LDAP?) which user principals can log into what hosts/accounts? -- Jos Backus jos at catnook.com

Hi, I was wondering if there is any of getting the gem package provider to run non-interactively? When upgrading mongrel it fails because it gets prompted for which version to install: Attempting remote update of mongrel Select which gem to install for your platform (x86_64-linux) 1. mongrel 1.1.1 (ruby) 2. mongrel 1.1.1 (jruby) 3. mongrel 1.1.1 (mswin32) 4. mongrel 1.1 (mswin32) 5.

Has anybody got privsep and compression working together on Solaris 2.6 and 2.5.1? I have no problem getting it working under Solaris 8, but on 2.5.1/2.6 it says: # ./sshd -p 6666 This platform does not support both privilege separation and compression Compression disabled -- ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ Kevin Currie | |

One particular use of Puppet would be to serve as a machine fact/configuration retrieval tool. So in order to produce a list of packages with version-release info installed on each machine something along the lines of the following code could be run: require ''puppet'' Puppet::Type.type(:package).defaultprovider.list.each do |package| puts

I wrote a patch to make the number of times and and the delay between retries that ssh attempts to talk to ssh-agent configurable. This patch is indispensible when running multiple ssh sessions in parallel from a script (e.g. to run commands on a large number of hosts); without the patch, many ssh sessions simply fail because they cannot contact the agent, rendering the mechanism unusable. If

For anyone that has experienced the odd End of file or Cannot describe errors, we''ve found that switching to Mongrel has fixed this problem for us. We''re currently running 5 instance of puppetmaster under mongrel (with the apache proxy in front) and things are going great. For more information on setting up Mongrel, visit:

OK. I got the rsync CVS code and compiled under Linux. That did the job, but only with --no-whole-file because of the local transfer. I then tried to read-batch... under Windows / Cygwin with the current Cygwin rsync. That didn't work - as expected. After compiling again under cygwin it worked! I can now create a diff from a new CD to the version before and send the diff files by email. On

Hi, I have an application which is dying horrible deaths (i.e. segmentation faults) in mid-flight, in production... And of course, I should fix it. But while I find and fix the bugs, I found something I think should be different - I can work on submitting a patch, as it is quite simple, but I might be losing something on my rationale. When Mongrel segfaults, it does not -obviously- get to clean

Just curious as to the functionality of puppet. Does Puppet ensure that a service is up and running as long as puppet is running? Ie, I want to make sure ssh is always running, if for some reason ssh get''s shut down, does puppet start it back up when it does it''s config sync run? Thanks! --------------------------------- Pinpoint customers who are looking for

I''m sure everyone has read and committed the Puppet Best Practice to memory by now (I joke). One of the things I''ve written in there deals with trailing commas, which I adopted from the way I used to do multiline in Perl, but I''ve noticed that most people don''t tend to do that in Puppet. Should I revise this or should we all start using the trailing commas?

Hi all, Not sure if this is a bug in puppet, yum, or just something I''m doing wrong. I''m trying to use puppet to update a package to a particular version and exec a command when that update is applied. The problem is, puppet calls yum which successfully updates the package, but puppet then thinks the update has failed and hence doesn''t trigger the exec. Next

Hi all; I am sure this question has been brought up before, but I could not find any information in the FAQ or docs etc. Quick question; Is there a way of syncing multiple servers simultaneously from 1 source server? Thanks, -- Vaibhav Goel extension 6347