11-02-2008
the Files are being deleted even when there was a process holding on to it..
If I am right you are using rm -f (force option to delete the files)
Now what u can do to avoid reboots is
fuser -dV /tmp
that will show you the list of delete files holding on by a process..
u can get the corresponding process id and purge them.
10 More Discussions You Might Find Interesting
1. UNIX for Dummies Questions & Answers
Hello,
does anyone have a script that can check the contents of the /tmp directory and for example e-mail the directory content if anything other than session files are present?
Maybe there are better ways to monitor suspicous /tmp and /var/tmp activity, if so I'm listening :) (1 Reply)
Discussion started by: jamesbond
1 Replies
2. UNIX for Dummies Questions & Answers
Hello,
Can someone please tell me which command to use to determine the available disk space on a given disk device?
I have to write a shell script that compresses files and stores them in a specific location but I am not sure how "conservative" I should be?
Thanks in advance!
Al. (4 Replies)
Discussion started by: alan
4 Replies
3. 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
4. Shell Programming and Scripting
Hi ,
I am a documentum consultant and facing a problem with a shell script that launches an installer to install documentum . The problem i am facing is that , when i invoke the below script to install the software it says -
The directory /tmp does not contain enough space to extract... (1 Reply)
Discussion started by: h.shergill
1 Replies
5. Shell Programming and Scripting
HI ...
I am New to the Unix...I am trying to write a script to check the disk space.
But i am not able to write it.
I know the command to check the disk space df -k,but unable to write the script..Can any body help me...
Thanks in advance... (3 Replies)
Discussion started by: Kingkon
3 Replies
6. Shell Programming and Scripting
Hi Guys
i have a nice little piece of code then i need to modify so that is does not look at /Voulmes/*
thanks
sub disk_full {
my $i = 0;
open( DF, "df -l|" );
while (<DF>) {
#chomp();
next if (/^\/proc\b/);
$i++;
next if ( $i == 1 );
... (3 Replies)
Discussion started by: ab52
3 Replies
7. Shell Programming and Scripting
Hi,
I am new to shell scripting, and want to monitor disk space using shell script continously on server, which will shoot mail after crossing threshold limit
Please suggest.
Regards
Manoj (1 Reply)
Discussion started by: manoj.solaris
1 Replies
8. Solaris
Hi ,
In a server /tmp has almost reached 75% and i can see the File system utilization is 48Mb only , so i believe some process is using the /tmp space. I would like to know which process is using /tmp space.
# df -h /tmp
Filesystem size used avail capacity Mounted on
swap ... (9 Replies)
Discussion started by: chidori
9 Replies
9. Solaris
Hello All,
I have solaris server running,
uname -a
SunOS host 5.9 Generic_112233-12 sun4u sparc SUNW,Sun-Fire-280R
Filesystem Size Used Available Capacity Mounted on
/dev/md/dsk/d0 9.8G 8.7G 1.0G 90% /
/dev/dsk/c1t1d0s3 4.3G 7.7M 4.2G ... (17 Replies)
Discussion started by: gull05
17 Replies
10. UNIX for Advanced & Expert Users
Hi Team
when I boot the server I get this 2 errors :
the disk drive for /tmp is not ready yet or not present
the disk drive for /boot is not ready yet or not present
and its stay like that , I m using Ubuntu 12.04
please if someone have any idea how to fix that problem . (1 Reply)
Discussion started by: SULTAN01
1 Replies
LEARN ABOUT DEBIAN
trimhistory
TRIMHISTORY(8) System Manager's Manual TRIMHISTORY(8)
NAME
trimhistory - Remove old Xymon history-log entries
SYNOPSIS
trimhistory --cutoff=TIME [options]
DESCRIPTION
The trimhistory tool is used to purge old entries from the Xymon history logs. These logfiles accumulate information about all status
changes that have occurred for any given service, host, or the entire Xymon system, and is used to generate the event- and history-log web-
pages.
Purging old entries can be done while Xymon is running, since the tool takes care not to commit updates to a file if it changes mid-way
through the operation. In that case, the update is aborted and the existing logfile is left untouched.
Optionally, this tool will also remove logfiles from hosts that are no longer defined in the Xymon bb-hosts(5) file. As an extension, even
logfiles from services can be removed, if the service no longer has a valid status-report logged in the current Xymon status.
OPTIONS
--cutoff=TIME
This defines the cutoff-time when processing the history logs. Entries dated before this time are discarded. TIME is specified as
the number of seconds since the beginning of the Epoch. This is easily generated by the GNU date(1) utility, e.g. the following com-
mand will trim history logs of all entries prior to Oct. 1st 2004:
trimhistory --cutoff=`date +%s --date="1 Oct 2004"`
--outdir=DIRECTORY
Normally, files in the BBHIST directory are replaced. This option causes trimhistory to save the shortened history logfiles to
another directory, so you can verify that the operation works as intended. The output directory must exist.
--drop Causes trimhistory to delete files from hosts that are not listed in the bb-hosts(5) file.
--dropsvcs
Causes trimhistory to delete files from services that are not currently tracked by Xymon. Normally these files would be left
untouched if only the host exists.
--droplogs
Process the BBHISTLOGS directory also, and delete status-logs from events prior to the cut-off time. Note that this can dramatically
increase the processing time, since there are often lots and lots of files to process.
--progress[=N]
This will cause trimhistory to output a status line for every N history logs or status-log collections it processes, to indicate how
far it has progressed. The default setting for N is 100.
--env=FILENAME
Loads the environment from FILENAME before executing trimhistory.
--debug
Enable debugging output.
FILES
$BBHIST/allevents
The eventlog of all events that have happened in Xymon.
$BBHIST/HOSTNAME
The per-host eventlogs.
$BBHIST/HOSTNAME.SERVICE
The per-service eventlogs.
$BBHISTLOGS/*/*
The historical status-logs.
ENVIRONMENT VARIABLES
BBHIST The directory holding all history logs.
BBHISTLOGS
The top-level directory for the historical status-log collections.
BBHOSTS
The location of the bb-hosts file, holding the list of currently known hosts in Xymon.
SEE ALSO
xymon(7), bb-hosts(5)
Xymon Version 4.2.3: 4 Feb 2009 TRIMHISTORY(8)