On 11/22/2014 10:46 AM, Carlos E. R. wrote:
On 2014-11-22 19:34, Lew Wolfgang wrote:
I'm not OP, and I'm also a bit late to this thread, but I recall an annoying issue with updatedb causing balkiness not too long ago. It wasn't immediately obvious what was going on and I doubt if a non-technical user would have figured it out. It can easily happen. That's why the current cron job nices and ionices it.
/etc/cron.daily/mlocate.cron:
# alter the priority of the updatedb process if [ -x /usr/bin/renice ]; then /usr/bin/renice +${NICE:-19} -p $$ > /dev/null 2>&1 fi if [ -x /usr/bin/ionice ] && /usr/bin/ionice -c3 true 2>/dev/null; then /usr/bin/ionice -c${IONICE_CLASS:-2} -n${IONICE_PRIORITY:-7} -p $$ > /dev/null 2>&1 fi
You can go further and use class 3. Although I don't understand some of the constructs above.
I just edited /etc/sysconfig/cron so that "DAILY_TIME" ran at 03:00 instead of 15-minutes after booting. This was for an always-on desktop. Regards, Lew -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org