I have the following script which writes the output of the scirpt in a log file in the same directory from which the script is run. I need the scipt to write the logs daily to a differnt directory with the date appended to the log on a daily basis.
The script is as follows...
.... (1 Reply)
Here is a puzzler.
To start, let me say that I've done a search on this issue and it is definitely not related to line endings being encoded in windows returns.
I get this error when I run SOME perl scripts. I have a script called hello_world.pl. I do $cp hello_world.pl new_hello_world.pl... (0 Replies)
Hi everyone,
Is there an efficient way to source all of the files contained in a directory? Theoretically I could create a FOR loop and successively source each file, but I just wanted to check if there was a cleaner method.
Thanks!
Mike (3 Replies)
Hi Folks,
I have logs at the following location
cd /out/app/logs/
now that logs directory contain different types of logs now sometimes i need to
do disk clean up activity so i need to zipped the logs can you please advise
any command by which all the logs created in this directory are... (2 Replies)
I have random connections coming into my FTP server, but the source IP is not showing up in my logs. Here is what my logs look for me trying to connect as a "whatever" user that doesn't exist. You can see there is no source IP telling me where this connection came from:
Jun 27 10:13:40... (4 Replies)
Hello Everyone,
I want to delete the image files from a directory, which are not listed in a TEXT file.
The directory contains large number of image files (in millions) required / not required. I want to delete the image files which are "not required".
I have generated a Text file having... (3 Replies)
As i am working in unix environment so i have an logs that is created by my application at the following location that is
/opt/app/glac/current/servers/ops/logs
inside the logs directory there are different kinds of logs(that is the file having extension as .log ) have been created... (1 Reply)
when I run the following command in AIX (bash),
find ./*
I get the following error.
find: bad status-- ./*
Thats becasuse, its an empty directory. The same works, when there the directory is not empty. Even though the find deesnt have to rerun any result.
My full find command would look... (4 Replies)
Hi All,
Daily i am doing the house keeping in one of my server and manually moving the files which were older than 90 days and moving to destination folder.
using the find command . Could you please assist me how to put the automation using the shell script .
... (11 Replies)
I keep getting this error and I am not sure why.
-bash: ./p4: /bin/ksh^M: bad interpreter: No such file or directory
First I run my makefile and this works fine:
goodmain: main.o
gcc -o goodmain main.o
main.o: main.c
gcc -c main.c
Then I want to limit my output so I... (11 Replies)
Discussion started by: cokedude
11 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)