Default process priorities

[Paul Lussier]

Bill McGonigle <bill at bfccomputing.com> writes:

> Does anybody know of a facility to specify default process priorities  
> on a per-executable basis?  I can't seem to find one, but I may just  
> be looking in the wrong places.

I don't know what platform you're one, but Debian has
/etc/default/<app name> where default stuff is placed.

All init scripts have something like this in them:

  test -f /etc/default/apache2 && . /etc/default/apache2

Mostly these files just set variables which get used within the init
script if set.  But I'm sure there's a way to coerce that mechanism to
do other stuff.

> * modify all the init scripts to desired nice value - lots of work,  
> can't handle updates well, could be lots of places a process gets  
> launched, not easy to share init scripts

- Everything you modify on a server ought to be in revision control.
- Everything you upgrade on a server ought to be tested before it goes
  into production so changes are known and understood.
- If changes are known and understood, the versions of files in
  revision control can be properly updated so they are correct for
  both the version and the desired/necessary local customizaitions.

The above 3 things are true, changes become much less painful.

If you have several servers all running the same app (apache for
instance) and the all require the same config, centralized rev control
makes this really easy.  If you have exceptions to the rule, a simple
branch or system specific version that gets mapped out of the rev
control is not difficult.

-- 
Seeya,
Paul