similar to: augeas lens asterisk

We were previously forcing the augeas Modprobe lens to match modules.conf and conf.modules. It turns out that the contents of these files are quite different to modprobe.conf, requiring a new lens. This change keeps the logic which looks for where modules should go, but doesn't update the augeas configuration. If there is no augeas lens for /etc/modules.conf, any attempt to parse or modify it

Add a directory to contain required augeas lenses which aren't yet upstream. Include a new lens for grub's device.map. --- augeas/README.txt | 4 ++++ augeas/device_map.aug | 28 ++++++++++++++++++++++++++++ 2 files changed, 32 insertions(+), 0 deletions(-) create mode 100644 augeas/README.txt create mode 100644 augeas/device_map.aug diff --git a/augeas/README.txt

Cheers all, With PR https://github.com/networkupstools/nut/pull/2425 I've paid some attention to the tools we have to help external consumers edit NUT configuration files. These go back to issues like https://github.com/networkupstools/nut/issue/2294 (originally posted for "nutconf" improvement, and now with some more TODO's linked to it) and

Hi, I tried to compile asterisk-1.8.0-beta4 but after ./configure && make I've got following error: [CC] res_fax.c -> res_fax.o [LD] res_fax.o -> res_fax.so [CC] res_fax_spandsp.c -> res_fax_spandsp.o res_fax_spandsp.c:117: error: field ?fax_state? has incomplete type res_fax_spandsp.c:118: error: field ?t38_state? has incomplete type res_fax_spandsp.c: In function

Greetings. I''m trying to find a few concrete examples of how to use augeas within a Puppet module, to make changes to a JSON file. I''ve been googling for the past hour and a half, and while I have found several pages which provide reference-type documentation, I have yet to see a single usable example. All of the augeas examples seem to demonstrate how to maintain a file for

Hi all, I''m trying to come up with a lens for the zabbix agent config files. I find the lens language untransparent at best, so I''m struggeling to figure out what''s up. The debugging possibilities are extremely limited. Here''s what I have now: zabbix.aug: ==== (** An adjusted copy of the postfix_main module **) module Zabbix_agent = autoload xfm

Add a function to display more complete augeas errors if they occur. Update all uses of augeas in GuestOS::RedHat to use it for error reporting. --- lib/Sys/VirtV2V/GuestOS/RedHat.pm | 185 ++++++++++++++++++++++++------------- 1 files changed, 121 insertions(+), 64 deletions(-) diff --git a/lib/Sys/VirtV2V/GuestOS/RedHat.pm b/lib/Sys/VirtV2V/GuestOS/RedHat.pm index cf8787d..8b211f0 100644 ---

Augeas now configures the Grub lens for /boot/grub/menu.lst by default. The code which was checking this was broken in the case where there was more than 1 included path. We now check if /boot/grub/menu.lst is included. If it is, we don't reload. If it isn't, we add it, but don't remove any other config first. This fixes RHBZ#586822 --- lib/Sys/VirtV2V/GuestOS/RedHat.pm | 25

On Mon, Sep 22, 2014 at 02:56:18PM +0200, Pino Toscano wrote: > On Monday 22 September 2014 13:50:18 Richard W.M. Jones wrote: > > On Mon, Sep 22, 2014 at 10:49:42AM +0200, Pino Toscano wrote: > > > The lenses in our custom path need the system lens for base > > > definitions. Disabling the system path was worthless anyway, since > > > our API does not allow

Hello everyone, I am currently trying to add elements to an XML file (a libvirt network definition) using Puppet (2.7.23)/Augeas (0.10). The XML looks like this: <network> <name>virbr0</name> <uuid>57fdc6e3-cba1-4110-88ef-850f1b71ee39</uuid> <forward dev=''eth0'' mode=''nat''/> <bridge

If Augeas fails to parse a file, more information is available in at least these fields: ><fs> aug-ls /augeas/files/etc/fstab/error /augeas/files/etc/fstab/error/char /augeas/files/etc/fstab/error/lens /augeas/files/etc/fstab/error/line /augeas/files/etc/fstab/error/message /augeas/files/etc/fstab/error/pos Pull out some of these fields and add them to the error message. The new error

(apologies in advance for the line wrap) I have the following tidbit of augeas code, which inserts a rule into /etc/sysconfig/iptables as the first rule of a specifically named chain; # augtool> insert append before "/files/etc/sysconfig/iptables/table/append[. = ''Mayo-Firewall-INPUT''][1]" # augtool> match /files/etc/sysconfig/iptables/table/append[. =

Hi! I using Augeas to handle dump and passno for certain mount points in /etc/fstab. Each mount point is defined as it''s own augeas block: augeas { ''homeLV'': context => ''/files/etc/fstab'', changes => [

what i thought would be a simple edit using augeas is turning out to not be so straight forward, can anyone please help ? the plan is to edit sendmail.cf and change the default DS to DShostname.domain class mail { $key = DS service { ''sendmail'':; } augeas { "sendmail.cf/$key": context =>

Don't carry around Augeas lenses. It is fragile, since if the lens is added to upstream Augeas but the version number has not changed, then Augeas won't parse the target file at all. This specifically causes password adjustments to fail in RHEL 7.1. In future, if we need an Augeas lens, it must be added to Augeas, either upstream or as a downstream patch carried around by distros. ---

On Monday 22 September 2014 13:50:18 Richard W.M. Jones wrote: > On Mon, Sep 22, 2014 at 10:49:42AM +0200, Pino Toscano wrote: > > The lenses in our custom path need the system lens for base > > definitions. Disabling the system path was worthless anyway, since > > our API does not allow user-specified custom paths. > > > > The only possible use for AUG_NO_STDINC

Hi, I was running puppet (2.7.5) on a host which needed to have some settings changed in it''s /boot/grub/menu.lst file. This file is however a link to /boot/grub/grub.conf When I used augeas in puppet like shown below augeas { "${dom0::params::module_label}_menu.lst_memory": incl => ''/ boot/grub/menu.lst'', lens => ''Grub.lns'', changes

The lenses in our custom path need the system lens for base definitions. Disabling the system path was worthless anyway, since our API does not allow user-specified custom paths. The only possible use for AUG_NO_STDINC to aug-init could have been to not load the lenses right at init time loading them later; however, this is what the AUG_NO_LOAD flag (= 32) does already. --- daemon/augeas.c | 5

On Mon, Sep 22, 2014 at 10:49:42AM +0200, Pino Toscano wrote: > The lenses in our custom path need the system lens for base > definitions. Disabling the system path was worthless anyway, since our > API does not allow user-specified custom paths. > > The only possible use for AUG_NO_STDINC to aug-init could have been to > not load the lenses right at init time loading them

On Fri, Apr 28, 2017 at 05:02:29PM +0300, Pavel Butsykin wrote: > > On 20.04.2017 12:19, Pavel Butsykin wrote: > >[This sender failed our fraud detection checks and may not be who they > >appear to be. Learn about spoofing at http://aka.ms/LearnAboutSpoofing] > > > >20.04.2017 10:54, Richard W.M. Jones пишет: > > > >>On Wed, Apr 19, 2017 at 04:58:56PM