Stephen, How about you first tell the ARS server to use a different log file name then grab the old file and load it up?
( It should work with any file other than arerror.log. Not sure that name can be changed.) -- Carey Matthew Black Remedy Skilled Professional (RSP) ARS = Action Request System(Remedy) Love, then teach Solution = People + Process + Tools Fast, Accurate, Cheap.... Pick two. On 9/12/06, Heider, Stephen <[EMAIL PROTECTED]> wrote:
List, I just wrote a program that imports the ARS log files (actually, any text file) into a form. It works fine and clears out the log files each time it's run. ARS evidently remembers the last byte offset of each log file - instead of simply appending text to the end of the log file. When ARS adds a new line to the file it starts writing at the last byte offset (end of the file). Here is what happens: 1. Log file has 60KB of entries. 2. Program is run and imports all entries in the log file into a Remedy form. 3. Log file size is 0KB. 4. ARS adds a new line to the log file. 5. Log file size is now 61KB. The first 60KB of the file is filled with Nulls. I tried running arsignal with different parameters. I realize that restarting the Remedy NT service will reset its internal byte offset counter, but that is not practical in a production environment. How can the byte offset of a log file be reset? Thanks. ARS 6.3 Windows Server 2003 Stephen
_______________________________________________________________________________ UNSUBSCRIBE or access ARSlist Archives at http://www.wwrug.org
