The Puppet Labs Issue Tracker has Moved: https://tickets.puppetlabs.com

Feature #3228

Add puppet.conf for process priority of puppetd

Added by Andrew Forgue about 4 years ago. Updated almost 4 years ago.

Status:AcceptedStart date:02/19/2010
Priority:LowDue date:
Assignee:-% Done:

0%

Category:plumbing
Target version:-
Affected Puppet version:0.25.4 Branch:
Keywords:

We've Moved!

Ticket tracking is now hosted in JIRA: https://tickets.puppetlabs.com

This ticket may be automatically exported to the PUP project on JIRA using the button below:


Description

It would be nice (no pun intended) to have a puppet.conf option that would specify the priority of the puppetd process. It appears that Ruby has a Process.setpriority that would do this. This way we wouldn’t have to worry about maintaining separate methods to set priority (whether SMF, SRC, /etc/init.d/puppet or otherwise).

History

#1 Updated by James Turnbull about 4 years ago

  • Category set to plumbing
  • Status changed from Unreviewed to Needs Decision
  • Assignee set to Luke Kanies

#2 Updated by Trevor Vaughan about 4 years ago

Alternatively/additionally (?) the ability to explicitly set the nice-ness of Exec’s and Services would be ideal.

The combination of the two would be extremely useful.

#3 Updated by Luke Kanies almost 4 years ago

  • Status changed from Needs Decision to Accepted
  • Assignee deleted (Luke Kanies)

Also available in: Atom PDF