truncating log files

Does any one have the best methodology to truncating log files - after several months of devlopment some of our logs - namely access.log and ddsync.log are 195 and 60 megs each?

I was hoping maybe IWOV had some script to run which cleaned things up but I don't see anywhere

Find more posts tagged with

Comments

Adam Stoller

Truncating log files is pretty simple - the difficulty comes in dealing with logfiles that are being held open by an existing process.

If you're on Unix - you can usually do something like: cat /dev/null > logfile and things work out reasonably well.

On Winows I'm not sure whether there is an equivalent (maybe? type nul > logfile ?)

--fish
(Interwoven Senior Technical Consultant)

Migrateduser

OK - I'm on Windows 2000 so the Unix commands won't work - the windows command
nul > name of log works but your right about the processes being used as I keep getting:

The process cannot access the file because
it is being used by another process.

so the services need to be shutdown for this to work

Adam Stoller

Yeah - on Windows you pretty much need to stop the services, rotate or truncate the log files, and then reboot in order to ensure being able to bring up TeamSite cleanly.

Check with support on possible feature requests that might already be on file related to this and/or to open up a new one if they cannot find an existing one.

--fish
(Interwoven Senior Technical Consultant)

StuFox

This should help - you don't need to stop the service to rotate the log.

I do it by firstly backing up the old log to a secondary spot (just in case).

Then I have a blank file called newlog.txt which I use to copy into the log file with the command

copy newlog.txt iwtrace.log

Cheers
Stu