search for: lensing

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

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 Friday 24 October 2014 16:00:15 Richard W.M. Jones wrote: > 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. I disagree with this patch, in the current situation. The

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

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. ---

Hi David, We have a general problem using Augeas in libguestfs and I wonder if you have any advice. The problem is that we often -- as with yesterday's patch -- add new config file paths to lenses. Or we want to parse config files which are not necessarily in the exact paths that Augeas is expecting. Now it's easy enough to parse such files using an arbitrary lens by calling

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

Ted Harding said: > I can get the estimated RRs from > RRs <- exp(summary(GLM)$coef[,1]) > but do not see how to implement confidence intervals based > on "robust error variances" using the output in GLM. Thanks for the link to the data. Here's my best guess. If you use the following approach, with the HC0 type of robust standard errors in the

Hello, Anyone wrote or uses augeas to manage splunk config files and care to share them? Thanks a lot. Mohamed. -- You received this message because you are subscribed to the Google Groups "Puppet Users" group. To post to this group, send email to puppet-users@googlegroups.com. To unsubscribe from this group, send email to puppet-users+unsubscribe@googlegroups.com. For more options,

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

Having just spent about 2 hours trying to work out how to add a password --md5 $1$Qejy8/$.qFUuDeYL.cuSDpN1ZD.S1 line to my grub.conf I thought it would be worth sharing how I finally got it to work. augeas {"/boot/grub/grub.conf": context => "/files/boot/grub/grub.conf", changes => [ "set timeout 15",

v3: - Don't remove the LVM transform.

v2 of previous patch, which fixes some missing bits. For now I'm going to go with Pino's RHEL 7.1 patch, since it is at least smaller than this. So I'm sending this to the list just to have it archived for later. Rich.

G''day my module''s init.pp: class mailaliases { if ($skip_mailaliases != "true") { mailalias { "root": # ensure => absent, ensure => present, target => "/etc/aliases", recipient =>

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

Experts— I’m attempting to export a keytab for a created SPN on the AD DC machine but I’m receiving an error: ERROR(runtime): uncaught exception - Key table entry not found File "/usr/lib64/python2.6/site-packages/samba/netcmd/__init__.py", line 175, in _run return self.run(*args, **kwargs) File "/usr/lib64/python2.6/site-packages/samba/netcmd/domain.py", line 129, in

(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[. =

Dear Arnaud, Now I started to write a driver that simulates continous power breaks. (E.g. in every 30 minutes.) This could be used for testing of setup of client upsmons. I have to simulate a behaviour of a real UPS. The physical model contains an extra attribute: the charging current that needed to compute recharge time and actual battery charge during the recharge process. Can we call this

Dear Arnaud, Now I started to write a driver that simulates continous power breaks. (E.g. in every 30 minutes.) This could be used for testing of setup of client upsmons. I have to simulate a behaviour of a real UPS. The physical model contains an extra attribute: the charging current that needed to compute recharge time and actual battery charge during the recharge process. Can we call this

It looks like isoinfo is in that package since openSUSE Leap 42.1, so make sure to include it to not break the isoinfo* APIs. --- appliance/packagelist.in | 1 + 1 file changed, 1 insertion(+) diff --git a/appliance/packagelist.in b/appliance/packagelist.in index 5cf2276..0a71cc3 100644 --- a/appliance/packagelist.in +++ b/appliance/packagelist.in @@ -136,6 +136,7 @@ ifelse(SUSE,1, dnl It