> You'll almost certainly get much better performance if you increase
OK, but let's fix this first.
I had a look but didn't find anything very useful. Will reread the logs
now... it seems useful though:
Oct 30 09:39:01 rhn /USR/SBIN/CRON[21777]: (root) CMD ( [ -x /usr/lib/php5/maxlifetime ] && [ -d /var/lib/php5 ] && find /var/lib/php5/ -type f -cmin +$(/usr/lib/php5/maxlifetime) -print0 | xargs -n 200 -r -0 rm)
No hangs on Oct 29.
Oct 28 02:39:01 rhn /USR/SBIN/CRON[5459]: (root) CMD ( [ -x /usr/lib/php5/maxlifetime ] && [ -d /var/lib/php5 ] && find /var/lib/php5/ -type f -cmin +$(/usr/lib/php5/maxlifetime) -print0 | xargs -n 200 -r -0 rm)
Oct 27 it did not hang.
Oct 26 14:39:01 rhn /USR/SBIN/CRON[5116]: (root) CMD ( [ -x /usr/lib/php5/maxlifetime ] && [ -d /var/lib/php5 ] && find /var/lib/php5/ -type f -cmin +$(/usr/lib/php5/maxlifetime) -print0 | xargs -n 200 -r -0 rm)
Seems to be a hang at Sunday at daytime when nobody was using it but
cron daemon.
These are all last lines in syslog before the crash, coming from
/etc/cron.d/php5:09,39 * * * * root [ -x /usr/lib/php5/maxlifetime ] && [ -d /var/lib/php5 ] && find /var/lib/php5/ -type f -cmin +$(/usr/lib/php5/maxlifetime) -print0 | xargs -n 200 -r -0 rm
so it runs twice an hour.
--
Meelis Roos (mroos@linux.ee)
--