similar to: Custom facts in current and old environments

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA512 Hello, I read and find a way (well, there seems to be several equal implementations) to collect the ssh keys of machines. However they all give only the choice to choose between the key formats. But is there a way to collect both keys of a machine, the rsa _and_ the dss key (and maybe the rsa1 too)? I didn''t find a way to solve this as

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA512 Hello, at the moment I fight with puppetdoc and end in a ruby confusion. To the problem: > puppetdoc --debug --trace --mode rdoc --all manifests/site.pp info: scanning: ["manifests/site.pp"] /usr/lib/ruby/1.8/puppet/util/rdoc.rb:82:in `output_resource_doc'' /usr/lib/ruby/1.8/puppet/util/rdoc.rb:82:in `sort''

Hello, when I store a file biger than 2GB to a samba server version 2.2.5 everythink works fine. But when I do that with a server version 2.2.6 or 2.2.7 the saving fails on the 2GB limit. The problem can be seen with windowsclients or with smbclient (any version > 2.2.5). I did some debuging and find that the lseek64 fails. But I didn't find the reason. Regards Klaus Ethgen

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Hello, first of all, please reply private as I am not subscribed to the list. But if this question takes to much traffic I can subscribe. My problem is that I have to use procmail (as it can call external programs) which finally calls deliver. My main rules are sieve and they work find except that I cannot use subaddress matching in envelope to (not

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA512 Hello, There seems to be just a bit to do with the latest openssh (5.8p1) and ControlPersist. I encountered two problems: 1. When I use ControlPersist in combination with ProxyCommand to reach a other host over that proxy I get the following message: Bad packet length 1397966893. Disconnecting: Paket corrupt When I fist ssh to

Hello, I am not sure if I trigger a bug and if so it could also be in ruby sqlite3 backend. However, maybe I do something totally wrong. I have the following part in puppet.conf: [master] storeconfigs = true dblocation = /var/lib/puppet/state/clientconfigs.sqlite3 dbadapter = sqlite3 Now every time a client (agent in puppet speak) is run I get one more connection to the

I'm hitting the 2G limit taring from 2.2.2 to ntfs NT4. could this be my problem as well. -----Original Message----- From: samba-admin@lists.samba.org [mailto:samba-admin@lists.samba.org]On Behalf Of Klaus Ethgen Sent: 29 November 2002 4:10 PM To: samba@lists.samba.org Subject: [Samba] Version 2.2.6 and above are not able to store big files over 2GB Hello, when I store a file biger than

I have created my first ''fact'', first attempt at Ruby too, and configured the fileserver to server it but when a Fedora (5 or 6) client sync''s puppetd appears to hang. CentOS clients sync and use the new fact fine. Find attached the fact file and the output from ''puppetd --debug --factsync'' on a FC5 client is below. This is a 0.20.1 client and

Hello, I''m trying to add an environment variable as fact like this : #export $FACTER_test="infof" #facter | grep test test => infof But my fact don''t synchronize with puppet master. I don''t see it in / var/puppet/yaml/clientfile.yaml If I want this works, I''ve need to start puppet like this : #puppetd -vt --factsync but factsync''s

fact loads: I use facter to search the rsync path and then i write this sudoers line: Cmnd_Alias BACKUPCOMMANDS = /usr/bin/rsync I call puppet like this: puppetd --factsync --server=xxx.yyy.61.131 --waitforcert 60 --test the recipe is: sudoensure_line { sudobackupcommands: ligne => "Cmnd_Alias BACKUPCOMMANDS = $rsyncpath",

I''ve checked out the page on adding custom facts for Facter and I see that there are a number of ways to do this. Is there a preferred method of setting system-wide facts? In this case, I''d like to set a "Location" fact which represents the data centre a server is in. Cheers, James *********************************************************************************

Is there a recommended way to set $FACTERLIB so that Puppet will be able to access custom facts when running as a Red Hat service? If I export $FACTERLIB=/var/puppet/facts and then run Puppet manually I have no problems, but I''m not sure how I should be setting $FACTERLIB when Puppet is running automatically. Cheers, James

I have some facter file to distribute before running puppet on the platform. The problem is : how can i send the facter local.rb file so the rest of the .pp file take into account the new facts created ? ex: i have sudopath as a facter fact and one sudoers class that need that sudopath to work. How do you model that ? it seems puppet would have to rerun after the new local.rb is downloaded

Hi, When starting puppet on a new machine, (or when the $vardir/lib is empty) puppet will not run the facts, it will only copy them. on the second time puppet runs, it works quiet well: on the client its defined: [main] pluginsync = true pluginsource = puppet://$server/plugins plugindest = $vardir/lib/puppet factpath = $vardir/lib/puppet/facter [puppetd] factsync = true I also tried with

Hi I''m trying to add extra facts to facter. The puppetd is running on Debian Etch Amd64 as Xen 3.1 guest. I''ve follow the Wiki on adding the facts. First I used relative path in the manifest and added "factsync=true" in client''s puppetd.conf. And then tested it with "puppetd -vt". But no matter what i tried, this error came: File paths must be fully

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 I''m just getting started with using Puppet, and from what I''ve seen I really like it. However, I''m trying get started with slighly more advanced things like templates but I''m running into a roadblock with not knowing what built-in variables I have available to me. Is there someplace this is documented?

I might have the terminology wrong, but how to a give new puppet providers to the puppet clients? I''m thinking a provider is the thing the puppet client uses to implement a task that the master has given it. Am I way off here? Mike B. ---------------------------------------------------------------- This message was sent using IMP, the Internet Messaging Program.

Some time ago i sent to the list a problem i was having with facts on fedora core 6 and wasn''t able to find a solution at that time, but with the release of RHEL5 and CentOS 5 based on fc6 i have hit the problem again. i have written several facts to collect information about a clients network and i am also using the vmware fact from the wiki. i have separated my original fact into

May I please ask again for some assistance with the question below? I hope somebody can help me. Thanks, Ed Greenberg -------- Original Message -------- Subject: Re: [Puppet Users] Using custom facts in Puppet Date: Tue, 16 Nov 2010 13:14:06 -0600 From: Ed Greenberg <edg@greenberg.org> Reply-To: puppet-users@googlegroups.com To: puppet-users@googlegroups.com On 11/16/2010 09:33

I''m working with a pretty simple config at the moment to track down some issues I''m seeing with custom facts and plugins. I have factsync = true (default locations) and I have a simple fact in /var/lib/puppet/facts/ (actually it''s David''s netmask plugin) my pp file I''m testing with contains only: notice "netmask: ${netmask}" puppet -v