Guys, I'm sorry.
I was a bit confused over how to reference template paths relatively
(I'm managing someone elses puppet deployment you see!).
I fully qualified the path to the template in the development tree, and
then copied to production. You can see below that my path is still
pointing
On Tue, Mar 08, 2011 at 12:30:05PM +, Tom Boland wrote:
> this is the contents of the template:
>
> SPAMDOPTIONS="-d -L -i <%= ipaddress_eth0 -%> -A 10.44.217.0/20 -A
> 10.216.15.242/32 -A 10.216.1.14/32 -A 10.216.15.0/24 -A
> 213.171.193.103/32 -m 40 -q -x -u spamd --min-children=40"
Change
On Tue, Mar 8, 2011 at 12:30 PM, Tom Boland wrote:
> Hi guys,
>
> I have the following which I use to set up /etc/sysconfing/spamassassin.
> One of the options in this file sets the listening interface to the IP
> address on eth0, and using a template seemed like a perfect way to achieve
> this, a
