Christopher:
You can run a script that does the renaming on your Sun using an if [ -e <filename> ] then mv filename newfilename
You can even use VARIABLES for the file name and run this in a loop.
James McKenzie
-----Original Message-----
From: Action Request System discussion list(ARSList) [mailto:[email protected]] On Behalf Of Pruitt, Christopher J
Sent: Wednesday, October 11, 2006 12:06 PM
To: [email protected]
Subject: Re: How to manage the Remedy Log Size
Sorry, I forgot to add some additional information.
We are running on UNIX SUN
Remedy AR System Version 6.03 Patch 15
Christopher Pruitt
Consultant Specialist
EDS - Bank of America
I3-Inventory IW Infrastructure Team
Phone: +1-972-605-7702 (8-835)
mailto:[EMAIL PROTECTED]
Confidentiality Notice: This message and any files transmitted with it are intended for the sole use of the entity or individual to whom it is addressed, and may contain information that is confidential, privileged, and exempt from disclosure under applicable law. If you are not the intended addressee for this e-mail, you are hereby notified that any copying, distribution, or dissemination of this e-mail is strictly prohibited. If you have received this e-mail in error, please immediately destroy, erase, or discard this message. Please notify the sender immediately by return e-mail if you have received this e-mail by mistake.
-----Original Message-----
From: Action Request System discussion list(ARSList) [mailto:[email protected]] On Behalf Of Eric Cleereman (IT)
Sent: Wednesday, October 11, 2006 2:01 PM
To: [email protected]
Subject: Re: How to manage the Remedy Log Size
Sorry, second to last line of that should have read:
if exist "%logpath%\%logname%.1" ren "%logpath%\%logname%.1"
"%logname%.2"
-----Original Message-----
From: Action Request System discussion list(ARSList) [mailto:[email protected]]On Behalf Of Eric Cleereman (IT)
Sent: Wednesday, October 11, 2006 2:57 PM
To: [email protected]
Subject: Re: How to manage the Remedy Log Size
Hi Christopher,
Under Windows 2000 SP2, I have a shell script which does the following:
if not exist "%logpath%\%logname%" goto :EOF
if exist "%logpath%\%logname%.99" del "%logpath%\%logname%.99"
if exist "%logpath%\%logname%.98" ren "%logpath%\%logname%.98"
"%logname%.99"
...
if exist "%logpath%\%logname%.1" ren "%logpath%\%logname%.2"
"%logname%.1"
ren "%logpath%\%logname%" "%logname%.1"
I schedule the script to run once a night, and have never had any problems with it. Each log maintains all the data it had previously, it's easy to find logs from any given date, and Remedy always creates a fresh log each day. Each fresh log starts right where I'd expect, with no extra padding at the top.
This has worked for us since Remedy 5. Which version of Remedy are you running?
Eric Cleereman
-----Original Message-----
From: Action Request System discussion list(ARSList) [mailto:[email protected]]On Behalf Of Christopher Pruitt
Sent: Wednesday, October 11, 2006 2:43 PM
To: [email protected]
Subject: How to manage the Remedy Log Size
Currently we have log files that grow to big. However, we do not what to lose previously entered data into those logs. Many times, we are asked to research what happened in regards to a data entry made yesterday or three days ago, or who ran a large query last Friday, for example.
We have been working on a script to truncate and restart our remedy logs.
Good news.... We have done lots of testing. The bad news is there is no clean way to do this without bouncing Remedy. Here are the two options we have tried....
1) Copy the current log file to a backup file then empty the log file.
2) Move the current log file to a backup then create a new log file with the original log files name.
Neither work.... Remedy keeps these log files open and keeps track of where the next record should be written. Given that...
Option 1 does not seem to work because, while it copies the current log file to a backup and "empties" the log file, the next record written to the log is written where Remedy believes the next record should be written. Therefore, we end up with a file with file with a lot of empty space and then a log record.
Option 2 doesn't work because, it does move the file to the backup and then creates an empty file, but then since remedy remembers the file address and were the next record should be written, it writes the next log records to the end of the backup file not to the current log file.
Given that, can anyone recommend a way to do this? We have though of trying to us the Maximum Log-File Size option to control the size of our logs, however, that does not address the over all issue of making copies of the logs for research purposes later on.
Any suggestions?
________________________________________________________________________
_______
UNSUBSCRIBE or access ARSlist Archives at http://www.wwrug.org
________________________________________________________________________
_______
UNSUBSCRIBE or access ARSlist Archives at http://www.wwrug.org
________________________________________________________________________
_______
UNSUBSCRIBE or access ARSlist Archives at http://www.wwrug.org
_______________________________________________________________________________
UNSUBSCRIBE or access ARSlist Archives at http://www.wwrug.org
