then %>
Then the templates started working as expected. It did NOT work when
I did this:
<% if has_variable?("server_admin") and server_admin != "" then %>
So the comparison operator is slightly different after converting to
a string.
- JimP
On Aug 20, 2009,
Hi,
I'm trying to generate apache virtual host configs and I have run
into what I think is a bug. Here is my setup:
CentOS 5.3
puppet 0.24.8
puppetmaster 0.24.8
Here is my template for the vhost configuration:
-- vhost2.erb --
NameVirtualHost <%= name %>:<%= port %>
:<%= port %>>
<% if has_v
Other solution would be to create a rsyslog type and call it in the
ossec::server class.
I have a sendmail class that has this syslog type:
syslog { "/var/log/maillog":
selector => "mail.debug",
ensure => present,
owner => root,
Do you have a
node default {
...
}
section in your site.pp or any included file?
- JimP
On Jun 3, 2009, at 7:12 PM, Jeremy Hansen wrote:
>
>
> Actually, puppet seems to be doing this for any NEW host. What
> went wrong?
>
> -jeremy
>
> Jeremy Hansen wrote:
>> This one is driving me a little
What version of puppet? also what is your path set to. I had a
problem on an older version of puppet (can't remember which one)
where i had '/etc' on my path and puppet was trying to use /etc/rpm
as the rpm command, but /etc/rpm is a directory and then failed.
It has been fixed in the mor
Just ran into a dependency issue with 0.24.8. The system was trying
to add a crontab entry for a user it had not yet created. I do have
the user being created with the user type.
I started to look into the code and it seems the user is not setup
with autorequire. My question is should it
I believe you do not need
start => true
you may need to set the name though:
name => 'svc:/network/postfix:default'
unless 'svcadm enable postfix' works as is (I do not have postfix on
my servers, but I can do 'svcadm enable smtp'
The enable => true means to execute the 'sv
I see the same dependency problem with ypbind and yp-tools that come
with Fedora/RHEL/CentOS.
Changing to using an exec seems broken. It prevents you from using
the builtin provider that puppet supplies.
- JimP
On May 1, 2009, at 11:36 AM, Jason Rojas wrote:
RPM circular dependencies h
I'm trying to bootstrap puppet on an existing server I have. I rely
quite a bit on custom facts in my setup. Is there a way that I can
have the facts be required in a recipe, maybe like this:
file { "/etc/foo.conf":
...
content => template("foo.conf.erb"),
require =>
uot;${base} dead but subsys locked"
return 2
fi
echo $"${base} is stopped"
return 3
}
So even though you provide a PID file, the status command looks first
in the process table (finding the puppetd --test) first.
I have worked around t
I have this recipe setup to maintain puppetd:
service { "puppet":
name => $operatingsystem ? {
Fedora => "puppet",
CentOS => "puppet",
Solaris => $kernelrelease ? {
"5.10" => "svc:/network/puppetd:default",
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
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
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 have these 2 types:
file {"/var/log/ipfw.log":
ensure => present,
mode => 600,
14 matches
Mail list logo
