reniced and systemd
-------------------

  reniced 1.23-1 dropped the deprecated initscript, so reniced is not
  run automatically after boot any more.  While this functionality
  could be replaced by a systemd unit, I decided against it:

  - The original idea of reniced is to act on long running system
    service processes.

  - Nowadays these services are mostly systemd units anyway.

  - systemd units can already be configured with overrides and it is
    possible to set IO priority, nice levels and other things that way.

  - Advantages of using systemd overrides are:
    
    - perfect service identification (no more grepping the process list)

    - immediate action on unit starts and restarts (not just once at boot)


  To make use of the systemd overrides for a service foo that comes with
  a foo.service unit, you could do something like this:

% systemctl edit foo.service

  Then add a section like this:

[Service]
Nice=10

  Use 'systemctl restart foo.service' to activate the change.

  From now on, systemd will combine your override with the original
  foo.service unit (use 'systemctl cat foo.service' to see this).  You
  won't even get "configuration file has changed" warnings on release
  upgrades.

  Use 'systemctl revert foo.service' to completely remove your
  override.

  For further information on the available systemd configuration
  options, see the SCHEDULING section in systemd.exec(5).


  If the systemd unit overrides do everything that you need, you
  should use them and uninstall the reniced package.


  If you still want to have reniced started by systemd, you will have
  to write a simple one-shot unit and think of an appropriate trigger
  for the unit (eg. after some other service has started).  I do not
  provide a unit for reniced because I can't think of a universal
  trigger condition to use as a default shipped with the package.


  If your use case is different from all this and you run reniced from
  cron or in some other way, then you should not be affected by the
  removal of the initscript at all and can continue to use reniced as
  before.  That's the reason why reniced has not been removed
  completely from Debian.

-- Christian Garbs <debian@cgarbs.de>  Thu, 11 Jan 2024 22:57:03 +0100
