10-05-2011
you should probably not delete .log files - if you want to make space empty them up but leave them where they are - just in case an application still uses them. If you delete logfiles still in use, than the application might crash or some other weird behaviours might occur, so better >file.log
As previous posters mentioned already, you can as well check for last access with 'find /tmp -atime' whatever timeframe you want to keep just to make sure you dont remove files that might still be needed. Removing anything not accessed in the last 7 days might be a rather safe bet.
regards
zxmaus
This User Gave Thanks to zxmaus For This Post:
10 More Discussions You Might Find Interesting
1. UNIX for Dummies Questions & Answers
Eventhough there is no visible feed to the /tmp dir, when I shut my apps engine it gets down to 4%. Upon restarting my engine, give it about 10-15 minutes and the /tmp gets to a 100% again.
My engine is running on AIX 4.3. Engines job is to process metapp (metacode to PDF) completed files and then... (2 Replies)
Discussion started by: buRst
2 Replies
2. UNIX for Dummies Questions & Answers
I am running AIX 3 4.
When I do a df I get:
Filesystem 512-blocks Free %Used Iused %Iused Mounted on
/dev/hd4 32768 10232 69% 1309 16% /
/dev/hd2 917504 86360 91% 19744 18% /usr
/dev/hd9var 131072 67712 49% 617 ... (11 Replies)
Discussion started by: szodiac
11 Replies
3. AIX
good morning
The /tmp filesystem is full at 99 %
I have do a "rm" but the size is the same.
so i think that a process is always alive, but how can i do to know it ? (because I have deleted some file in /tmp)
thank you (9 Replies)
Discussion started by: pascalbout
9 Replies
4. Red Hat
i heard once that the /tmp directory was a ramfs (swap) that is cleared at reboot time, is this still the case in redhat EL 3 and 4 ? (1 Reply)
Discussion started by: BG_JrAdmin
1 Replies
5. Solaris
Can you help. My server sunning solaris 9 on x86 platform pretty much hung for a few hours... I could not use telnet or ssh to the box - it kept refusing connection. A few hours later - I was able to log in again.
The server has not rebooted but here are the first errors in the messages log... (5 Replies)
Discussion started by: frustrated1
5 Replies
6. AIX
The /tmp is 100% full, I found there are the following big files/directory:
1301500 syslog.out.58
166692 vac
158552 install.dir.2928686
158552 install.dir.2236636
110980 install.dir.2887698
/tmp/vac have some files like :
.toc ... (3 Replies)
Discussion started by: rainbow_bean
3 Replies
7. AIX
Hi,
I would like to know if /tmp file system is full, wheather it will affect the peformance of application installed on AIX. if Memory and CPU are not heavily utilized.
Regards,
Manoj. (1 Reply)
Discussion started by: manoj.solaris
1 Replies
8. Solaris
Hello all,
The issue is
# df -h /tmp
Filesystem size used avail capacity Mounted on
swap 4.0G 4.0G 8.7M 100% /tmp
# du -sh /tmp/
87M /tmp
By now you probably will say that this is open file destriptor issue.
Well no, nothing... (2 Replies)
Discussion started by: click
2 Replies
9. Emergency UNIX and Linux Support
Dear community,
my sql and apache server (with CMW installed) hangs due to /tmp full:
root@cms:~# df -h
Filesystem Size Used Avail Use% Mounted on
/dev/sda3 224G 27G 186G 13% /
tmpfs 3.9G 0 3.9G 0% /lib/init/rw
udev 3.9G ... (7 Replies)
Discussion started by: Lord Spectre
7 Replies
10. Solaris
Hi everybody,
few days ago we had a big issue with one of our solaris10 server.
Suddenly while my colleague was working on it for some troubleshooting he realized that the performance started to degrade.
At the end it reached the point that was not even possible to login usng the local console... (7 Replies)
Discussion started by: bdegiovanni
7 Replies
LEARN ABOUT CENTOS
abrt.conf
ABRT.CONF(5) ABRT Manual ABRT.CONF(5)
NAME
abrt.conf - Configuration file for abrt.
DESCRIPTION
abrt is a daemon that watches for application crashes. When a crash occurs, it collects the problem data and takes action according to its
configuration. This document describes abrt's configuration file.
The configuration file consists of items in the format "Option = Value". A description of each item follows:
DumpLocation = directory
The directory where should abrt store coredumps and all files which are needed for reporting. The default is /var/tmp/abrt.
MaxCrashReportsSize = number
The maximum disk space (specified in megabytes) that abrt will use for all the crash dumps. Specify a value here to ensure that the
crash dumps will not fill all available storage space. The default is 1000.
WatchCrashdumpArchiveDir = directory
The daemon will watch this directory and call abrt-handle-upload on files which appear there. This is used to auto-unpack crashdump
tarballs uploaded via ftp, scp, etc. The directory must exist and be writable for abrt. There is no default.
DeleteUploaded = yes/no
The daemon will delete an uploaded crashdump archive after an atempt to unpack it. An archive will be delete whether unpacking finishes
successfully or not. The default value is no.
SEE ALSO
abrtd(8) abrt-action-save-package-data.conf(5) abrt-handle-upload(1)
AUTHORS
o ABRT team
abrt 2.1.11 06/18/2014 ABRT.CONF(5)