reniced names suggest that it is a demon, consantly
running and monitoring system and changing nice level.

Unfortunetly, reniced is called in init, but it is one-shot
application of renice, just for programs started before it.

Essentially it is impossible with it, to renice new programs (like programs
a user on workstation starts, or after logging via ssh, or
after other deamon, i.e. apache, mysql restart).

It would be MUCH more usefull if renice will sit in loop,
and every 30 seconds or so, check if list of processes
changed, if it is so, than aplay rules to new ones.

If possibly it could use netlink to monitor for forks,
and execvs, to make it much more efficient.

Currently i just have script which loops
while true; do
 /usr/bin/reniced; sleep 30
done


Thanks.

The name 'reniced' comes from the fact that it 'renices daemons'.

I concur that the name might be confusing, but I won't rename the
whole project.  The package description should remove any ambiguity:
'renice running processes based on regular expressions'.

Your quick solution running in a while loop looks good to me.
Reacting to fork events across all processes would be a very different
program and something completely different than current reniced.
That's a new project.

That being said, the world has turned since 2010 and nowadays I would
not use reniced any more but instead call 'systemctl edit foo.service'
to add a 'Nice=' setting to the '[Service]' group (see systemd.unit(5)
and systemd.exec(5)).
The resulting drop-in file should survive Debian release updates
without prompting any conffile-conflicts (like there would be if
you added a nice(1) or renice(1) command to the old initscripts).

Sorry for the late reply, I'm currently in springtime cleaning mode ;-)

Regards
Christian