Dear All,
I had solved the problem earlier of CPU wait state being almost 100% and
had solved the problem of disbling the cron job of tmpwatch
-rwxr-xr-x 1 root root 290 Jul 5 21:24 tmpwatch
which is a cron.daily file
now more investigations reveleved to me that
since im running havp 0.89 with squid
i have a directory created by havp in
/var/tmp
drwxrwx--- 2 havp havp 71536640 Jul 14 18:15 havp
now if i do a cd /var/tmp
i go to tmp directory which is fine
then if i say
cd havp
my machine hangs and i see that the cpu wait state shoots upto 100%
now i tried goin in asingle user mode and the same problem
i ty to delete this directory i cannot
actually since the tmpwatch cron job was clearing files in /var/tmp/havp
it was hangging
apprecite some help n advice how to get reid of this directory
Regards
Fabian
> fabian wrote:
>> Dear Guys
>>
>> Thanks and apprecite your quick replies
>> By the way i had stated solving the problem of almost 100% CPU
>> utulization
>> starting everyday at 4 am and ending at 10 am in a very crude way
>> top was reporting 95% wa
>>
>> i started to check the crontab file and noticed that the
>> cron.daily entry in the file sarts at 4 am
>>
>> and in the directory i found
>>
>>
>> -rwxr-xr-x 1 root root 133 Jul 6 16:59 00webalizer
>> -rwxr-xr-x 1 root root 379 Jul 6 17:02 0anacron
>> lrwxrwxrwx 1 root root 39 Nov 9 2008 0logwatch ->
>> /usr/share/logwatch/scripts/logwatch.pl
>> drwxr-xr-x 2 root root 4096 Jul 5 21:25 backup
>> -rw-r--r-- 1 root root 62 Jul 6 17:37 clamav
>> -rwxr-xr-x 1 root root 118 Jul 6 17:00 cups
>> -rwxr-xr-x 1 root root 456 Nov 3 2008 freshclam
>> -rwxr-xr-x 1 root root 26 Jul 6 17:00 havp
>> -rwxr-xr-x 1 root root 180 Dec 2 2007 logrotate
>> -rwxr-xr-x 1 root root 418 Jan 6 2007 makewhatis.cron
>> -rwxr-xr-x 1 root root 137 Jul 6 17:23 mlocate.cron
>> -rwxr-xr-x 1 root root 2181 Jun 21 2006 prelink
>> -rwxr-xr-x 1 root root 114 Jul 6 17:01 rpm
>> -rwxr-xr-x 1 root root 290 Jul 5 21:24 tmpwatch
>>
>>
>> i started movies some of thes files to difereent directory and finally
>> found that it was the below file that was the culprit
>>
>> -rwxr-xr-x 1 root root 290 Jul 5 21:24 tmpwatch
>> -------
>> the contents of the file was
>>
>> /usr/sbin/tmpwatch -x /tmp/.X11-unix -x /tmp/.XIM-unix -x
>> /tmp/.font-unix \
>> -x /tmp/.ICE-unix -x /tmp/.Test-unix 240 /tmp
>> /usr/sbin/tmpwatch 720 /var/tmp
>> for d in /var/{cache/man,catman}/{cat?,X11R6/cat?,local/cat?}; do
>> if [ -d "$d" ]; then
>> /usr/sbin/tmpwatch -f 720 "$d"
>> fi
>> done
>> ----------------
>>
>> now everything works fine without this file in the /etc/cron.daily
>> directory
>> so the tmpwatch was the culprit cause the CPU wait state to almost 99 %
>> for almost 6 hrs
>> but jus would like to know if this particular script has any signifance
>> or
>> any perfomance issue and my system will run perfect without the file
>>
>>
>> apprecite you help
>>
>>
>> regards
>>
>> Fabian
>>
>>
>>
> man tmpwatch shows that this is designed to cleanup tmp directories -
> you may want to see why your tmp files are either very many or have some
> other issues
> HTH
> Rob
>
>
> --
> This message has been scanned for viruses and
> dangerous content by MailScanner, and is
> believed to be clean.
>
> _______________________________________________
> CentOS mailing list
> CentOS at centos.org
> http://lists.centos.org/mailman/listinfo/centos
>
--
This message has been scanned for viruses and
dangerous content by MailScanner, and is
believed to be clean.