Bug#316930: Updatedb doesn't run 'find' at the nice priority set in updatedb.conf
On Tue 05 Jul 2005, Andreas Metzler wrote: On 2005-07-04 David Jarvie [EMAIL PROTECTED] wrote: Package: findutils Version: 4.2.22-1 My /etc/updatedb.conf contains (among other things): LOCALUSER=root export LOCALUSER NICE=19 export NICE and when updatedb is run by cron from /etc/cron.daily/find, it runs at the expected nice priority of 19. However, when updatedb runs 'find', find's nice level is 0, not 19. [...] Hello, The cause of this is this that since very recently invoking su uses the PAM module pam_limits.so which in turn resets the nice-level to 0. http://bugs.debian.org/311058 http://bugs.debian.org/241663 As a workaround you can disable the entry for pam_limits.so in /etc/pam.d/su. (Gaining that the nice-level is kept, but losing safeguardlimits imposed on processes run with su.) A workaround could of course be to export the NICE value as something unique like FINDUTILS_NICE (to avoid unfortunate conflicts with other things), and then modify /usr/bin/updatedb to add nice -n $FINDUTILS_NICE in the su -c parameter. Paul Slootman -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#316930: Updatedb doesn't run 'find' at the nice priority set in updatedb.conf
On 2005-07-04 David Jarvie [EMAIL PROTECTED] wrote: Package: findutils Version: 4.2.22-1 My /etc/updatedb.conf contains (among other things): LOCALUSER=root export LOCALUSER NICE=19 export NICE and when updatedb is run by cron from /etc/cron.daily/find, it runs at the expected nice priority of 19. However, when updatedb runs 'find', find's nice level is 0, not 19. [...] Hello, The cause of this is this that since very recently invoking su uses the PAM module pam_limits.so which in turn resets the nice-level to 0. http://bugs.debian.org/311058 http://bugs.debian.org/241663 As a workaround you can disable the entry for pam_limits.so in /etc/pam.d/su. (Gaining that the nice-level is kept, but losing safeguardlimits imposed on processes run with su.) cu andreas -- See, I told you they'd listen to Reason, [SPOILER] Svfurlr fnlf, fuhggvat qbja gur juveyvat tha. Neal Stephenson in Snow Crash http://downhill.aus.cc/ -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#316930: Updatedb doesn't run 'find' at the nice priority set in updatedb.conf
Package: findutils Version: 4.2.22-1 My /etc/updatedb.conf contains (among other things): LOCALUSER=root export LOCALUSER NICE=19 export NICE and when updatedb is run by cron from /etc/cron.daily/find, it runs at the expected nice priority of 19. However, when updatedb runs 'find', find's nice level is 0, not 19. Running /etc/cron.daily/find manually as root produces the same result. The output from running it manually and then checking the status with 'ps -eo %p %P %n %a' was: 28410 4824 0 /bin/sh /etc/cron.daily/find 28412 28410 19 /bin/sh /usr/bin/updatedb 28420 28412 19 /bin/sh /usr/bin/updatedb 28422 28412 19 /usr/bin/sort -z -f 28423 28412 19 /usr/lib/locate/frcode -0 28426 28420 0 /usr/bin/find / -ignore_readdir_race ( -fstype NFS -o -fstype nfs -o -fstyp I'm running Debian testing i386, with kernel 2.6.8, with libc6 2.3.2.ds1-22. This bug really makes my system slow down until find finishes - it would be really useful to have it fixed. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
