new package 'killer' vs. 'and' (auto nice daemon) // Re: Replace LTSP show blocker FAM by GAMIN?
Am Montag 14 September 2009 schrieb RalfGesellensetter:
> Additionally, I installed auto nice daemon (and; discussed before),
> but don't have the time to tweak it on. Hence, configurations of
> other users would be great.
Scanning bug reports, I met the "killer" package introduced in 2008.
Of course, it was not installed in Etch, and thus not added by simple
upgrading (what other packages have to been added?).
So, I point myself here to
>$ apt-cache show killer
>Maintainer: Debian Edu Developers <firstname.lastname@example.org>
>Depends: perl, exim4 | mail-transport-agent
> Description: Background job killer
> killer is a perl script that gets rid of background jobs. Background
> jobs are defined as processes that belong to users who are not
> currently logged into the machine. Jobs can be run in the background
> (and are exempt from *killer*'s actions) if their scheduling priority
> has been reduced by increasing their nice(1) value or if they are
> being run through condor.
> When the package is installed, a cron job is installed to run killer
> once an hour.
In worst case this can mean that you have to wait 1 hour until CPU is
released. Is anybody using AND (auto nice daemon) additionally, or is it
better just to adjust the timing of the cronscript?