Not ab augeas expert but IIRC what I did in a similar situation is force
puppet/augeas to point to only one file.
Try adding "context," "incl," and "lens" to your augeas definition, like
the example below. By specifying the lens, I think it helps speed up the
augeas type also. At least I read th
Greg Coit [24.09.2013 00:48]:
>
> BTW, still playing with augeas too - the most recent code is:
>
> augeas { 'vsftpd.conf':
> context => '/files/vsftpd/vsftpd.conf',
Greg,
shouldn't this be '/files/etc/vsftpd/vsftpd.conf'?
Just a guess from a novice...
Regards,
Werner
--
--
You rec
LOL - or I could just use one of the 2 vsftpd modules on puppetforge... I
never *intend* to do things the hard way. :)
Greg
On Tuesday, September 24, 2013 9:32:53 AM UTC-7, Greg Coit wrote:
>
> I've decided to not be blocked by this issue and to have puppet manage the
> config file. It's no
I've decided to not be blocked by this issue and to have puppet manage the
config file. It's not an ideal solution, but good enough until I learn
more about either augeas or inifile.
Greg
On Monday, September 23, 2013 3:48:05 PM UTC-7, Greg Coit wrote:
>
> Nathan,
>
> Thanks for the response -
Nathan,
Thanks for the response - I did not know about inifile.
I unfortunately seem to be having trouble with ini_setting - the following
causes a new line to be added every time puppet gets run:
ini_setting { 'anonymous_enable':
path=> '/etc/vsftpd/vsftpd.conf',
setting => 'anon
Greg,
I believe resource ini_setting would be appropriate here but I do
understand the desire to learn about Puppet + Augeas.
> augeas { 'vsftpd.conf':
> context => '/etc/vsftpd/vsftpd.conf',
> changes => [ 'set anonymous_enable=NO', 'set chroot_local_user=YES',
],
> require => File
On 15/02/12 08:10, Steve Shipway wrote:
> This is only a guess, but is Augeas doing a STRING comparison of the values
> instead of a NUMERICAL one?
>
> String-wise, "7000" < "80" but numerically it's the other way around.
>
> Can you try setting the current value to '1' and see if Augeas wants
This is only a guess, but is Augeas doing a STRING comparison of the values
instead of a NUMERICAL one?
String-wise, "7000" < "80" but numerically it's the other way around.
Can you try setting the current value to '1' and see if Augeas wants to change
it to 784009728. If it does, then that'
