--- SI Reasoning <[EMAIL PROTECTED]> wrote:
> I dug a little deeper and I think I found the cron that caused things to kick
>
> out. This had not been a problem until this weekends update:
>
> find / -name core -atime +5 -exec rm -f "{}" ';'
>
> I use this program to delete old crons so that they do not just sit and eat
> hard drive space. Why is this causing a complete crash now?
You should be careful!! All that is named "core" is not necesarily a coredump!
You need more that a one-liner to do this. You need to test each file with the
"file" command and grep for something like "core file". I could not come up
with a one-liner find for that ... does any one have one?
=====
________________________
Eugenio Diaz, BSEE/BSCE
Linux Engineer
[EMAIL PROTECTED]
__________________________________________________
Do You Yahoo!?
Get email alerts & NEW webcam video instant messaging with Yahoo! Messenger
http://im.yahoo.com
