search for: manifested

top-level kickstart file contains only includes, example custom-template.ks is provided with documented customization points. Signed-off-by: Alan Pevec <apevec at redhat.com> --- recipe/common-manifest-post.ks | 31 +++++++++++ recipe/common-manifest-pre.ks | 11 ++++ recipe/common-post-chroot.ks | 46 ++++++++++++++++ recipe/common-post.ks | 24 +++++++++

So I'm new to using wine. I recently purchased a used macbook, and installed wine to see if I could get System Architect 3.0 to run. System Architect is a program to allow plugging into various amplifiers and dbx Driverack units to make changes on your computer more than what you can do on the limited menu of the unit. Installing wine was fine (I used macports to install), and upon trying to

hello list!! I am still having some file sharing issues with this puppet server and I was hoping someone would have an opinion they could share on this situation ## puppet errors err: //basefiles/File[/etc/yum/pluginconf.d/priorities.conf]: Failed to retrieve current state of resource: Error 400 on SERVER: Not authorized to call find on /file_metadata/acadaca/yum/pluginconf.d/priorities.conf

I was using Photoshop CS5 on my Ubuntu 11.04 system fine. I did an update of wine, now it won't work. I have tried to uninstall and reinstall wine, and copied the PS install from windows, it still has errors. > -desktop:~$ wine "c:\Program Files\Adobe\Adobe Photoshop CS5\Photoshop.exe" > wine: Call from 0x7b839f22 to unimplemented function msvcp90.dll.??0?$basic_string at

Hi As I''m more familiar with cfengine and it''s way to split updates (in update.conf) from the actual grunt work (in cfagent.conf), I''m wondering how to best manage puppet and my manifests with puppet...? Should I define a puppet class that copy the puppet package (in .tgz format) and all the manifests to the client, and then have all my other classes depend on

So I''m trying to get multiple environments to work with puppet 0.25.1 on ubuntu 8.04 and no matter what I do, puppet just completely ignores any environment setting. There''s really next to no information in terms of configuration on the multiple environments documentation page (http://reductivelabs.com/trac/puppet/wiki/UsingMultipleEnvironments) other than saying that the

Hi, I want to validate my puppet manifests before I check them into source control. I just want to make sure that the manifest syntaxes are legal, not to do any more complex testing - the checkin may be on my laptop and not on the system that the manifests may be intended to run on. Ideally I''d be able to do this from ruby code - and I did try to instantiate some classes and override

This series fixes and enhances parsing of the OVA manifest file. The changes are: - Added mandatory space to the regexp - Process all lines in the file, not just one - Warn on improperly formated lines - Support SHA256 hashes v1 -> v2: rebased on to master to make use of the Checksums module Tomáš Golembiovský (2): v2v: ova: fix checking of the manifest file v2v: ova: support SHA256

Hi, I am using a template to create an /etc/exports file. I have a template that looks like this (but results in the puppetmasterd dying on the server when the client updates): <% nfsHomeClients.split.each do |host| -%> /nfs <%= host %>(<%= mainshareoptions %>) <% nfspaths.each do |path| -%> <%= path %> <%= host %>(<%= nfsoptions %>) <% end

I also made the changes below in the puppet.conf file to tell puppet where to look for the the modules and manifests. I then restart the puppet master then ran puppet command to apply changes to a puppet client it did not find anything to change just got these three lines "info: Caching catalog for pdlnx-adpt03.kareoprod.ent, info: Applying configuration version

--- MANIFEST | 1 + 1 files changed, 1 insertions(+), 0 deletions(-) diff --git a/MANIFEST b/MANIFEST index 13897af..3489ff1 100644 --- a/MANIFEST +++ b/MANIFEST @@ -18,6 +18,7 @@ MANIFEST This list of files MANIFEST.SKIP META.yml po/es.po +po/fr.po po/it.po po/Makefile po/PACKAGE -- 1.6.5.2

hello again list!! I am attempting to work out how to serve files with puppet. Here is my fileserver.conf file # This file consists of arbitrarily named sections/modules # defining where files are served from and to whom # Define a section ''files'' # Adapt the allow/deny settings to your needs. Order # for allow/deny does not matter, allow always takes precedence # over

hi All, I''m a bit new to puppet. Is there a mailing list for puppet beginners?:) I have a service module called postfix, which defines file in a class: file { ''/etc/postfix/main.cf'': owner => "root", group => "root", mode => 644, content =>

This series fixes and enhances parsing of the OVA manifest file. The changes are: - Added mandatory space to the regexp - Process all lines in the file, not just one - Warn on improperly formated lines - Support SHA256 hashes v1 -> v2: rebased on to master to make use of the Checksums module v2 -> v3: - changed debug/warning messages in first patch according to Richard's suggestions

OK... I have relaid out my puppet dir as recommended in best practices: [jleggett@binford puppet]$ find . -print | grep -v .svn . ./plugins ./plugins/lines.pp ./files ./files/module ./files/module/SSH ./files/module/SSH/ssh_config ./files/module/SSH/sshd_config ./files/module/INFO ./files/module/INFO/motd ./files/module/INFO/issue ./files/module/NIS ./files/module/NIS/nsswitch.conf

Hi List, Puppet Version: v2.7.13 Question - If I correctly setup multiple manifestdir''s in the puppet.conf file how can I import a node pp file located in a different directory tree to site.pp? My configuration information is below. In my puppet.conf file I have setup an environment called "stable", within this environment I have setup the manifestdir, modulepath and

This series fixes and enhances parsing of the OVA manifest file. The changes are: - Added mandatory space to the regexp - Process all lines in the file, not just one - Warn on improperly formated lines - Support SHA256 hashes v1 -> v2: rebased on to master to make use of the Checksums module v2 -> v3: - changed debug/warning messages in first patch according to Richard's suggestions

Hi, I''m not using puppet in a standard way (ie. in a server/client configuration), just the standalone ''puppet --use-nodes'' command. I''m having problems with the directory structure of modules and using the import feature. My directory infrastructure looks like this: /srv/puppet/facter/... /srv/puppet/manifests/site.pp /srv/puppet/manifests/libs/file.pp

The regular expression for parsing the manifest line was wrong. There is a mandatory space between '=' and the hash. Another problem was that only the first line of the manifest file was actually processed. Also added some debugging info and warning to catch problems with parsing. Signed-off-by: Tomáš Golembiovský <tgolembi@redhat.com> --- v2v/input_ova.ml | 8 +++++++- 1 file

Hi there, I''m running puppetmasterd manually while testing, and I was trying to split my manifest in several parts using import. If I do so whenever I run the puppetmasterd the manifest gets loaded and served correctly: cognos ~ # puppetmasterd -v info: Starting server for Puppet version 0.20.0 info: Parsed manifest in 0.02 seconds info: /var/lib/puppet/files: allowing *.example.org