12 Commits

Author	SHA1	Message	Date
jasper	f18f86b9a0	adjust the uid puppet looks at to determine if a user is a "system user" to 1000. ... this then gets used to purge all non-system users, whether this is a good idea is left as an exercise to the user. ok aja@ (MAINTAINER)	2013-04-16 13:25:52 +00:00
ajacoutot	23308d862b	PKG_ARCH=*	2013-03-20 06:55:19 +00:00
ajacoutot	c00b663a00	Add a README to introduce integration with MCollective and ActiveMQ. ... ok robert@ (maintainer)	2013-03-18 15:07:56 +00:00
ajacoutot	a142354caf	Tweak on comment.	2013-03-15 14:57:25 +00:00
ajacoutot	f2bf574479	Factorize a bit more since both ports version share a lot. ... While here, fix the rc script to start the master instead of the client and vice-versa. ok robert@ (maintainer)	2013-03-13 14:35:38 +00:00
ajacoutot	735feab5d5	Do not hardcode paths in the rc scripts.	2013-03-13 09:56:19 +00:00
robert	e667c24c76	security update to 2.7.21	2013-03-12 18:52:11 +00:00
ajacoutot	ad17537ced	Install the proper puppet.conf.	2013-03-11 12:54:29 +00:00
ajacoutot	a710cb2a84	Remove CVS ID so that patch applies properly.	2013-03-08 16:24:39 +00:00
ajacoutot	fe50c78307	Start services with '-f' since they may not be enabled in rc.conf.local(5). ... Implement a restart command for the service provider and use '-f' as well. No need to specify a 'stop' common, our rc.d(8) is generic enough. ok robert@ (maintainer)	2013-03-08 16:19:15 +00:00
ajacoutot	b4063acc8b	Remove the ldap patches which aren't needed anymore. ... ok robert@ (maintainer)	2013-03-08 16:15:33 +00:00
ajacoutot	f615377661	Split ruby-puppet: ... * move the current port to ruby-puppet/3 * add a new puppet-2.7.X port under ruby-puppet/2 This allows us to ship with 2 different versions of Puppet. Since the Enterprise version is still running 2.7, we want to have a matching client because running puppet3 against a puppet2 server is highly discouraged and will mostly no work correctly. ok jasper@, robert@ (maintainer)	2013-03-08 16:12:47 +00:00