Well, I've worked around this for now by:
- uninstalling puppet and facter with mac ports (so there's no
puppetfoo executables under /opt/local/sbin or /opt/local/bin anymore
- used gem to install puppet and facter into the system ruby, so now
the executables are under /usr/bin/puppetfoo
This als
if this happens on a 0.25.5 server (and maybe client), it might be happening
because of the zaml implementation, can you reproduce this problem with
0.25.4 master?
in anycase, it sounds like a bug :)
Ohad
On Wed, Jun 16, 2010 at 9:35 AM, Nigel Kersten wrote:
>
>
> On Tue, Jun 15, 2010 at 6:32
On Tue, Jun 15, 2010 at 6:32 PM, donavan wrote:
> On Jun 15, 2:39 pm, "Gus F." wrote:
> > I am using puppet (version 0.25.5-1.e15 for redhat) for password
> > management for non-system users. This morning, users on some of my
> > puppet clients had their encrypted password strings in /etc/shado
