puppet - [no description]

Age	Commit message (Collapse)	Author	Files	Lines
2014-04-14	Reading even old sysconfig file	Michal Hrusecky	1	-0/+1
	For compatibility reasons reading even the old sysconfig file although new one overrides it. But people who have some interesting settings in the old sysconfig file can still use them unless the are set to something else in the new one.
2014-04-07	Make relation between service and sysconfig file obvious	Michal Hrusecky	1	-1/+1
	There is puppet service but it's environment file is called puppetagent (probably due to historical reasons). Making the naming more consistent and obvious.
2014-04-07	Adding dependency on puppetmaster to puppet	Michal Hrusecky	1	-1/+1
	Sounds like a good idea to wait with start of puppet agent to finish starting of puppet mater first.
2014-04-07	Use no-daemonize and not forking service	Michal Hrusecky	2	-6/+2
	Making puppet fork and systemd to read PID file seems unnecessary complicated.
2013-10-03	(#22660) Revert Fedora 17+ agent service name to "puppet" from "puppetagent".	Jason Antman	1	-0/+0
	Due to pull request 1166, in the fedora 17+ transition to systemd, the puppet agent service was inadvertantly renamed from "puppet" to "puppetagent". - in specfile, move systemd service and unit file names back to "puppet" from erroneous "puppetagent" - Add symlink to puppetagent unit file for compatibility with current bug - Alter package removal actions to deactivate and stop both service names - rename unit file in source tree to correspond with this
2013-02-19	(#19323) ext/systemd: adding a way to specify cmd line options	Vaidas Jablonskis	2	-4/+4
	This patch adds a way to easily specify extra command line options for both puppetagent and puppetmaster services when starting them with systemd. It removes ExecPre command as the directory creation is now handled by the RPM install. Previously there was no way to pass in valid puppet agent/master command line parameters like '--config=/etc/puppet/puppetmaster.conf', etc. A lot of people use separate config files for the agent and the master services. To make it somewhat consistent I added a systemd supported way to read environment variables from a file '/etc/sysconfig/<servicename>', so people who use extra cmd line options already will be able to do that with systemd as well. When services are started by systemd, systemd will read the files which contain the below variables and will pass their values when starting puppet services (I used the same variable names as it's been used in redhat-like distros already): PUPPET_EXTRA_OPTS in /etc/sysconfig/puppetagent PUPPETMASTER_EXTRA_OPTS in /etc/sysconfig/puppetmaster
2012-09-17	systemd unit files added on own branch for pull request to satisfy issue ↵	Niels Abspoel	2	-0/+26
	16144 : https://projects.puppetlabs.com/issues/16144