errors.log file growing very large

[Bill Sanderson]

I just checked out a Windows 2000 machine I'd installed the beta
on--probably on the day it was released.

The error.log file had reached about 3.8 gigs, and the system partition was
close to full.

I uninstalled the beta, and moved the file to another partition to try to
take a look at it--but I'm not sure what the right tool is to open a text
file that large!

I've seen other reports here of large and rapidly growing Errors.log files,
but hadn't run into it directly--now I have!

 

[John]

2000 and XP Notepad should open a txt file of any size.

 

[Bill Sanderson]

Have you tried them on large files? I believe I did on this one and got an
instantaneous "not enough memory" error.

 

[John]

While I have not tried a GB sized file, I have opened several hundred
megabytes in Notepad. You could try textPad, http://www.textpad.com/

It is a very useful app.

 

[Bill Sanderson]

Thanks - If I let it grow accidentally again, I might need that reference.

 

[Kaspars]

WinHex
http://www.x-ways.net/winhex/index-m.html
Tested on 11GB
Trial version can save up to 200kB
file size to view is virtually unlimited

 

[Bill Sanderson]

So--I reinstalled on that same machine, and did a full scan, and so far,
errors.log is 87 bytes long.

Still watching.

 

[John]

Weird - You scared me though - I went checking but none were more than 1 or
2 KB.

 

[Bill Sanderson]

my guess is that there will turn out to be some interaction with multi-use.

This server often has two administrative Remote Desktop/terminal services
sessions running, and the program UI and system tray icons are available in
all the sessions.

So far I've strictly left it alone and let it scan at night, but I'm sure
I'll experiment eventually.