similar to: Bug or misconfiguration? Trying to add local user in NIS environment

Hi there, i have a problem with the NOTIFYCMD in the upsmon.conf file. My line in the config looks like this: NOTIFYCMD "/etc/nut/upsnotify.sh" Now this ist my "/etc/nut/upsnotify.sh": #!/bin/bash EMAIL='mail at domain.de' SMS1='+49123456789' SMS2='+491987654231' #eMail versenden echo -e "Die USV mit dem Namen '$UPSNAME' hat seinen

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

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

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

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

Greetings - Maybe I''m a bit slow, but I''ve been trying to understand how to use a module for the better part of a day and I''m not getting it. Here''s what I''ve done: Using puppet 0.23.2 1. Downloaded the shorewall module from David Schmitt''s git repo (Thanks David!!!!) and placed it in the directory /var/lib/puppet/modules (using the rpm

On Thu, 28 Mar 2024 20:10:32 +0100 Kees van Vloten via samba <samba at lists.samba.org> wrote: > A local daemon will use /etc/nsswitch.conf to lookup UIDs and Winbind > can supply them. > > In addition I make (domain) users member of these local groups: > > audio,video,dialout,cdrom,floppy,lpadmin,plugdev,bluetooth,netdev,pulse-access,users > > Some users also

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

Greetings - Does anyone have plans for a Puppet BOF at LISA this year? I''ve seen some talk on the LOPSA configmgmt list about Config Mangement BOF''s, but nothing focused on Puppet. Please, Please, mom, can we have a BOF, PUHLEESE!!!! Luke - I hope you''ll be there so I can at least buy you dinner and beers/drinks for making my SA life easier with Puppet. Cheers, Jeff

On 02/13/2018 03:49 AM, Charles Lepple wrote: > On Feb 12, 2018, at 11:53 PM, David Melik wrote: > > On 01/21/2018 05:53 AM, Charles Lepple wrote: >>> If you hook up a terminal emulator to the comms port (1200 baud, 8/N/1 unless stickers and/or configuration DIP switches indicate otherwise), and type "f" <return>, do you get a status line like one of the

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",

Greetings - I''ve just started testing Puppet and have a couple of questions: 1. Is there a way to dynamically change a configuraion file that is sent to nodes? For example, I want to modify /etc/hosts to have the hostname and ip address set dynamically - the hosts file shoule look like: 12.34.56.78 node1.example.com 22.35.66.99 server1.example.com But I don''t want to

Group - I''m putting a presentation together for $work (a large .gov) and I want to make sure I get my facts (pun intended) straight ... Are the following steps for Facter-Client-Server interaction correct (I have a feeling not): 1. Client puppet run is initiated (via regular schedule, puppetrun, or puppetd) 2. The client contacts the server and downloads any custom facts it does not

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

My head hurts from trying to figure this out for the past several hours . . . I want to determine what provider to use based on a fact (thanks for the suse version fact btw) but I ain''t gettin it: What''s wrong? Am I going down the completely wrong path? Is there a better way? # suse-yum.pp case $suse_repo_name { #sled10-i586: {Package{ provider => rug}} sled10-i586:

On Thu, 28 Mar 2024 19:25:33 +0000 Rowland Penny via samba <samba at lists.samba.org> wrote: > On Thu, 28 Mar 2024 20:10:32 +0100 > Kees van Vloten via samba <samba at lists.samba.org> wrote: > > > A local daemon will use /etc/nsswitch.conf to lookup UIDs and > > Winbind can supply them. > > > > In addition I make (domain) users member of these local

Hello All, I''m using the "Branch Testing" approach documented at https://reductivelabs.com/trac/puppet/wiki/BranchTesting and am seeing an issue with certificates. On all clients, I can run puppetd --masterport=8141 successfully but see the following error when I run against the default (8140) port: err: Could not retrieve configuration: Certificates were not trusted:

I''ve got one node that doesn''t seem to want to load my custom fact. I''ve got ''factsync = true'' in my puppet.conf, and I know I can manually go onto the node and issue a ''puppetd -vt --factsync'' to get it to sync up, but I''d like to know why its not picking this fact up, because this could become problematic. Any tips on

Hi, I think the answer is no but is it possible to have a facter output from within puppet ? If i type facter on the command line i miss all the fact that puppet download with the factsync feature. How to see the output of facter including those of the factsync file ? -- Cordialement, Ghislain _______________________________________________ Puppet-users mailing list

Hi, Is it possible to block the port scanning through shorewall, if yes then how? Thanks and Best Regards, Arif