Hi
>> Is this the expected behavior, is there a workaround or is it simply
>> a bug?
>
> I don't think I completely understood your examples, but it's expected
> behaviour that Puppet will not manage through recursion any files
> you're explicitly managing.
I think you got it. :)
> To Puppet, t
On Fri, 20 Mar 2009 17:32:12 +0500, Mike Renfro wrote:
YUPI! SOLVED
That variant is ok!
exec { "/usr/bin/chpass -p '\$1\$HvjTWzzz\$jF.G/mEbh7IOtpCdUPUTO1' pt_":}
Thank everybody who helps me.
>
> nick.maystre...@gmail.com wrote:
>> On Fri, 20 Mar 2009 06:18:42 +0500, jrojas
>> wrote:
>> Am
nick.maystre...@gmail.com wrote:
> On Fri, 20 Mar 2009 06:18:42 +0500, jrojas wrote:
> Am I understand you right? I must exec this string "/usr/bin/chpass -p
> \$1\$HvjTWzzz\$jF.G/mEbh7IOtpCdUPUTO1 pt_"
> If yes, so it is not work((
> PS This is my "new" config string which NOT working as I wa
On 2009-Mar-20, at 2:07 AM, nick.maystre...@gmail.com wrote:
> PS This is my "new" config string which NOT working as I want: exec {
> "/usr/bin/chpass -p \$1\$HvjTWzzz\$jF.G/mEbh7IOtpCdUPUTO1 pt_":}
Have you tried single quotes? (I'm not sure if you even need to keep
the backslashes with sin
On Mar 19, 2009, at 6:23 PM, Luke Kanies wrote:
On Mar 18, 2009, at 1:23 PM, Jim Pirzyk wrote:
I have been working on full feature syslog type and providers. I
have a few questions about how to do things.
1) How do I have a type 'implement' functionality from another type.
For example, I
Hi
> I just though of another case where this would be useful, running
> 'newaliases' after /etc/mail/aliases has been updated. What do
> other people do? I have
>
> mailalias { foo:
> ...
> notify => [ Exec[newaliases] ]
> }
>
> on each mailalias type. I thought last night t
On Mar 20, 2009, at 10:00 AM, Peter Meier wrote:
Hi
I just though of another case where this would be useful, running
'newaliases' after /etc/mail/aliases has been updated. What do
other people do? I have
mailalias { foo:
...
notify => [ Exec[newaliases] ]
}
on each mail
Hi,
I've setup puppet to install apache2 version 2.2.9-7 (which isn't
available to the client).
Puppet installs apache-2.2.8-1ubuntu0.3.
Isn't it suppose to fail instead, when I've defined a version it can't
install?
This is my apache2 class:
class apache2 {
$packagelist = ["apache2"]
package
Hi folks,
I've searched around the group and couldn't find something that would
specifically answer my problem. I was trying to use puppetrun to force
an update on a specific host machine but ended up with the following
error:
# puppetrun --host client1.int
Triggering client1.int
err: Could not
Hi there,
this is not really a puppet reltated question but maybe someone who
uses puppet on freebsd machines has bumped into the same problem.
I want puppet to take care that certain ports are installed or updated
which works fine ...
... as long as there is no user input during the installation
I found that according to a comment in the apt provider, it does not
yet support enforcing versions :(
I guess I'll have to implement it, if I really need it :)
On 20 Mar., 15:32, "Klavs Klavsen" wrote:
> Hi,
>
> I've setup puppet to install apache2 version 2.2.9-7 (which isn't
> available to t
Hi All,
I wanted to make a module of mine to be more re-usable by declaring a
variable somewhere in it. I wanted users to be able to override the
variable, but I also wanted the module to work if they instantiated the
class directly. I'm using puppet 0.24.5 (and the -3 debian subversion)
and I fo
12 matches
Mail list logo
