search for: adminfil

Hi folks, I''m about to propose to my current company that we use puppet to manage releases of home grown software. The environment is a mix of Solaris 8/9/10 and RHEL 5&6. I''ve got a handle on how to create recipes to release software into the RHEL environment. The unknown for me is how to manipulate the pkgadd provider to load the locally grown package stream. Can

Greetings, I have a solaris package stored on a puppet server. I''d like to be able to maintain the package on a client system without having to also keep a copy of the package file on the client system. (think lots and lots of packages) Checksums work okay for noticing changes on the fileserver, but it seems that I have to keep a local copy of the file as well. When I rev the package

On Aug 27, 2006, at 9:55 AM, Thorsten Sandfuchs wrote: > hio, > me again :) > > In Debian, there is a mechanism to preseed debconf (configuration- > database for > the system) with decisions, before installing a package. Debconf > mussn''t ask > the user then. I wrote this pp for preseeding-support: [snip] Very cool. Seems like that''s something that

>> You''re right, if the package content from the global zone is >> reflected in all zones, the necessary files are already there. >> >> Typically I try to keep additional installed packages as >> independent as possible. So all additional software packages have >> the following parameters set in the pkginfo file: >> >>

...load when using "puppet:/// explorer/install_stb.sh" as a source as it takes too long and Puppet chops it off as a timeout. Yes, I know I can do it through a package resource, but the SUNWsneep component won''t install then - running "pkgadd -d http://server/SUNWsneep.pkg -a adminfile -r responsefile" does not work - pkgadd refuses to do a response file with a http datastream. So what does everyone think? Is a HTTP source for files feasable? --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups &quo...

..."18 - 23", repeat => 1 } define deadlypkg { tag("package") $pkgrepo="/staging/PRODUCTION/deadly" package{"$name": source => "$pkgrepo/$name.pkg", ensure => latest, adminfile => "puppet", schedule => nightly } } class deadly { deadlypkg{blah:} } This is all in a single manifest file, init.pp for the module "deadly". The node has "include deadly" in its definition. (Don''t worry about the silly na...