mail from cron with error at usr/lib/sa/sa2 -A (Opensuse 10.1)
Linux - ServerThis forum is for the discussion of Linux Software used in a server related context.
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Introduction to Linux - A Hands on Guide
This guide was created as an overview of the Linux Operating System, geared toward new users as an exploration tour and getting started guide, with exercises at the end of each chapter.
For more advanced trainees it can be a desktop reference, and a collection of the base knowledge needed to proceed with system and network administration. This book contains many real life examples derived from the author's experience as a Linux system and network administrator, trainer and consultant. They hope these examples will help you to get a better understanding of the Linux system and that you feel encouraged to try out things on your own.
Click Here to receive this Complete Guide absolutely free.
First do "df -h /var/log/sa" to see what filesystem it is on (likely root [/] or /var).
Second run "ls -l /var/log/sa" and see what you get.
Third run "find /var/log/sa" and see what you get.
It could be that the filesystem is mounted read only (which should stop ls or find from working but would stop new files from being created in it). More likely the filesystem is corrupted and you need to run an fsck against it. This should be done with the filesystem unmounted - if it is / or /var you'll likely need to boot to single user to do the fsck. If, however, /var/log/sa is a separate filesystem you should be able to unmount it and do the fsck.
WARNING: If this is / or /var you want to make sure you have a good backup before doing the fsck. If the corruption is caused by a disk failure the disk could be made worse by the fsck.
Last edited by MensaWater; 12-02-2011 at 09:47 AM.
file $(which find) to fi
/usr/bin/find: ELF 32-bit LSB executable, Intel 80386, version 1 (SYSV), for GNU/Linux 2.6.4, dynamically linked (uses shared libs), for GNU/Linux 2.6.4, stripped
to: cannot open `to' (No such file or directory)
fi: cannot open `fi' (No such file or directory)
- with the "find /tmp":
find: /tmp: No such file or directory