In a Remedy Phase 1 Filter (`!) do the following: Action 1: This will turn OFF the Logs Push to the Configuration ARDBC form Push If: 'Name' = "Debug-mode" No Requests Match: Take No Action Any Requests Match: Modify All Matching Set Value = 0
Action 2: Call your script to move the files Action 3: This will turn ON the Logs Push to the Configuration ARDBC form Push If: 'Name' = "Debug-mode" No Requests Match: Create New Request Any Requests Match: Modify All Matching Set Value = 164095 (or whatever value you need) The Configuration ARDBC form is a Vendor form installed with 6.3 that allows you to maintain the ar.conf file from inside Remedy workflow, the User Tool, or even Mid-Tier. Fred -----Original Message----- From: Action Request System discussion list(ARSList) [mailto:[EMAIL PROTECTED] On Behalf Of Christopher Pruitt Sent: Wednesday, October 11, 2006 1: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
