search for: lenses

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 to aug-init could have been > > to not load...

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

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

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 user-specified custom paths. > > > > > > The only possible use for AUG_NO_STDINC to aug-init could have been &g...

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

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 aug_transform, eg: $ ls passwd $ augtool -r `pwd` augtool> transform passwd incl /passwd augtool&g...

...hostnames must resolve hostname->IP address and # IP address->hostname. Server=backend.yomamma.com # Server port for sending active checks #ServerPort=10051 # Unique hostname. Required for active checks. === And the augeas output (all empty): == [/etc/puppet] # augparse /usr/share/augeas/lenses/contrib/zabbix_agent.aug [/etc/puppet] # augtool -e ls /files/etc/zabbix/zabbix_agentd.conf == Any help would be sincerely appreciated :) cheers, -- Walter Heck -- follow @walterheck on twitter to see what I''m up to! -- Check out my new startup: Server Monitoring as a Service @ http://...

...LM.R system("wget http://www.ats.ucla.edu/stat/stata/faq/eyestudy.dta") library(foreign) dat <- read.dta("eyestudy.dta") ### Ach, stata codes factor contrasts backwards dat$carrot0 <- ifelse(dat$carrot==0,1,0) dat$gender1 <- ifelse(dat$gender==1,1,0) glm1 <- glm(lenses~carrot0, data=dat, family=poisson(link=log)) summary(glm1) library(sandwich) vcovHC(glm1) sqrt(diag(vcovHC(glm1))) sqrt(diag(vcovHC(glm1, type="HC0"))) ### Result: # > summary(glm1) # Call: # glm(formula = lenses ~ carrot0, family = poisson(link = log), # data = dat) # Dev...

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

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.

...target => "/etc/aliases", recipient => "linuxroot+ $hostname@example.org", notify => Exec["newaliases"], } } } does nothing, my client continues to look like : [root@puppetslave lenses]# grep root: /etc/aliases #root: marc what am i missing? from the recipes i''ve looked at (and the one post on here which i just completely failed to understand) i''m not gathering what the magic incantation is that''s lacking. cheers chakkerz --~--~---------~--~...

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

...tried adding another SPN without the realm, and exporting without the realm, and I did not receive an error. I then deleted both SPNs via samba-tool spn delete, recreated the SPN using the realm just to make sure I’m not completely crazy and didn’t fat finger anything (and to make sure my contact lenses are making me see what I think I’m seeing) and I still get the error. When I do samba-tool spn list web-intranet-macmini, I see the SPN(s) associated with that user, and they are correct. Is there something glaringly obvious I’m missing? Mike

...config/iptables.save/error/line = 3 Debug: Augeas[firewall_omnibus_tcp_4100](provider=augeas): /augeas/files/etc/sysconfig/iptables.save/error/char = 0 Debug: Augeas[firewall_omnibus_tcp_4100](provider=augeas): /augeas/files/etc/sysconfig/iptables.save/error/lens = /shares/nfs/unixarch/share/augeas/lenses/dist/shellvars.aug:163.12-.99: Debug: Augeas[firewall_omnibus_tcp_4100](provider=augeas): /augeas/files/etc/sysconfig/iptables.save/error/message = Syntax error Debug: Augeas[firewall_omnibus_tcp_4100](provider=augeas): /augeas/files/etc/sysconfig/iptables.orig/error/pos = 64 Debug: Augeas[firewall...

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

....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 seems no other augeas package depends on it. augeas-lenses btrfsprogs + cdrkit-cdrtools-compat cryptsetup dhcpcd dhcp-client -- 2.9.3