>
>
> In this case, the link between the differring blocks should be
> externalized from your ldap module (e.g. the ldap module should care
> about stuff related to ldap.. not about relations to other modules).
>
> You could put the order declaration in a "node type" or "node role" kind
> of class
Hello
in James Loope's book (called Managing Infrastructure with Puppet), he
writes on page23: "The password hash can either be mined out of a
shadow file or generated with the mkpasswd utility." My question is:
how can the hash field be mined out of the shadow field. I tried to
use the generate f
On Sun, Jan 29, 2012 at 07:26:13AM -0800, Olivier wrote:
> Hello
>
> in James Loope's book (called Managing Infrastructure with Puppet), he
> writes on page23: "The password hash can either be mined out of a
> shadow file or generated with the mkpasswd utility." My question is:
> how can the hash
On Sun, Jan 29, 2012 at 11:39:46PM +0100, Stefan Schulte wrote:
> On Sun, Jan 29, 2012 at 07:26:13AM -0800, Olivier wrote:
> > Hello
> >
> > in James Loope's book (called Managing Infrastructure with Puppet), he
> > writes on page23: "The password hash can either be mined out of a
> > shadow file
and then lookup the hash in the /etc/shadow file
> or use the mkpasswd utility (with which I am not familiar)
>
> Once you have the hashed value of your desired clear text password
> you can copy&paste that in the user definition.
>
> -Stefan
>
your answer is just the text of my original question
On Sun, Jan 29, 2012 at 6:18 PM, Olivier wrote:
[snip]
>
> your answer is just the text of my original question. So the question
> still stands: how do I get the hashed value from /etc/shadow?
Are you trying to get a value from /etc/shadow on a managed node or
from the puppet master system itself
Since it's the shell redirection that Puppet seems not to like, why not
wrap the commands in a shell script and use generate on that?
On Jan 29, 2012 6:18 PM, "Olivier" wrote:
> and then lookup the hash in the /etc/shadow file
> > or use the mkpasswd utility (with which I am not familiar)
> >
>
On Mon, Jan 23, 2012 at 1:45 AM, Jos Houtman wrote:
> I am looking for advice/best-practices on how to handle inter module
> dependency's.
In general, I try and think of module dependencies and organization as
a matter of composition. Discrete modules themselves should avoid
establishing relati
On Fri, Jan 27, 2012 at 5:20 AM, Felix Frank
wrote:
> Jeff has made a strong point against using virtual resources in modules
> at all, causing me to shift my own views as well.
> If I understand him correctly, one of the chief problems is the high
> probability of accidental collection/realisatio
Nigel,
I just wanted to add, if we do go this route, we should work to support
private "forges" (module repos) as well.
Cheers,
Brian
On Sun, Jan 29, 2012 at 1:39 AM, Brian Gupta wrote:
> Nigel,
>
> It frightens me a bit that I think the "correct" solution, will be to
> replicate what the distr
10 matches
Mail list logo