I''ve just put it out; hopefully the packagers will get it in place
soon. Here''s the changelog:
Execs now autorequire the user they run as, as long as the user
is specified by name. (#430)
Files on the local machine but not on the remote server during
a source copy are now purged if purge => true. (#594)
Providers can now specify that some commands are optional (#585).
Also, the ''command'' method returns nil on missing
commands,
rather than throwing an error, so the presence of commands
be tested.
The ''useradd'' provider for Users can now manage
passwords.
No other providers can, at this point.
Parameters can now declare a dependency on specific
features, and parameters that require missing features
will not be instantiated. This is most useful for
properties.
FileParsing classes can now use instance_eval to add
many methods at once to a record type.
Modules no longer return directories in the list of found
manifests (#588).
The crontab provider now defaults to root when there is no
USER set in the environment.
Puppetd once again correctly responds to HUP.
Added a syntax for referring to variables defined in
other classes (e.g., $puppet::server).
STDIN, STDOUT, STDERR are now redirected to /dev/null in
service providers descending from base.
Certificates are now valid starting one day before they are
created, to help handle small amounts of clock skew.
Files are no longer considered out of sync if some properties
are out of sync but they have no properties that can create
the file.
--
Seize opportunity by the beard, for it is bald behind. --
Bulgarian Proverb
---------------------------------------------------------------------
Luke Kanies | http://reductivelabs.com | http://madstop.com
在 1 May , 2007，24:00，Luke Kanies 写道：> I've just put it out; hopefully the packagers will get it in place > soon.The OS X Package appears to be stable, but has not been extensively tested. By request, the launchd configuration files are no longer selected by default. http://reductivelabs.com/downloads/packages/OSX/puppet-0.22.4 +facter-1.3.7.mpkg.zip _______________________________________________ Puppet-users mailing list Puppet-users@madstop.com https://mail.madstop.com/mailman/listinfo/puppet-users
Hi, thank you for this. I think it would be very wise to create two packages, one for puppetmaster and the other one for the client. But it would definetly be a wise idea not to launch puppetmaster by default. I think this is what you do right now. I have disassembled the previous package you had created, took the postinstall scripts (which load puppet and puppetmaster into launchd) out of it. I had created a second package which enables puppet in launchd and also created the configuration file needed to contact the right server. I think this can somehow be created automagically... Tomorrow is a new day that I will be able to spend with this issue, maybe I come up with a script or installer interface to create /etc/ puppet/puppetd.conf during install of the package. Great times ahead, udo. On 01.05.2007, at 18:28, Benjamin C. Kite wrote:> > 在 1 May , 2007，24:00，Luke Kanies 写道： > >> I've just put it out; hopefully the packagers will get it in place >> soon. > > > The OS X Package appears to be stable, but has not been extensively > tested. > By request, the launchd configuration files are no longer selected by > default. > > http://reductivelabs.com/downloads/packages/OSX/puppet-0.22.4 > +facter-1.3.7.mpkg.zip > > > _______________________________________________ > Puppet-users mailing list > Puppet-users@madstop.com > https://mail.madstop.com/mailman/listinfo/puppet-users >-- ---[ Institute of Cognitive Science @ University of Osnabrueck ---[ Albrechtstrasse 28, D-49076 Osnabrueck, 969-3362 ---[ Eyes: http://www.zoide.net/ ---[ Ears: http://www.auriculabovinari.de/ _______________________________________________ Puppet-users mailing list Puppet-users@madstop.com https://mail.madstop.com/mailman/listinfo/puppet-users