Package: killer Version: 0.90-8 Severity: important Although no documentation is present in /usr/share/killer, I did get from the description of the package that if I want to run a script in background on a system where killer is been ran from a cron script, I have two options: a) install and use "condor" b) increase the niceness of the process.
However the second does not seem to work. Here is how I reproduce: 0) you must have on your system at least 1 user (let's call it "someuser") not currently logged in, plus root 1) in a virtual terminal (but _not_ inside the desktop environment), log in as root 1a) verify that the root user results as logged if you run "w" 2) give the command "sudo -u someuser nice -n 1 sleep 100" 2a) verify that everything is as expected with "ps -u someuser -U someuser l" 3) in another terminal, run "sudo killer" Result: the process is killed (if there is a lesson to take, being nice doesn't help with killers). If you add to this that option a) is not available to ordinary users, this becomes annoying. Is there something I'm missing? Or was there a change in ps output that killer was not warned about? -- System Information: Debian Release: jessie/sid APT prefers testing APT policy: (650, 'testing'), (600, 'unstable'), (500, 'oldstable-updates'), (400, 'experimental') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 3.12-1-amd64 (SMP w/2 CPU cores) Locale: LANG=it_IT.utf8, LC_CTYPE=it_IT.utf8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Versions of packages killer depends on: ii exim4 4.82-3 ii exim4-daemon-light [mail-transport-agent] 4.82-3 ii perl 5.18.2-2 killer recommends no packages. killer suggests no packages. -- no debconf information
signature.asc
Description: This is a digitally signed message part
