Files in Eset Logfile folder choking up System drive

[Bordonbert 0]

Hi all.  I am running ESSP in Win10 on a good old fashioned "upright" PC of modern spec.

My System SSD is not huge and is being choked up by Eset's logfiles.  They currently stand at over 65GB.  It has reached the point where Eset's daily updates can fail because of lack of space.  I would like to have answers to a few simple questions if anyone can help.

Is the default location C:/Program Data/Eset/... fixed or can it be defined within settings somewhere.  I am aware that centralising program data is a "good thing" Windowswise, but in a case like this it may be necessary.  I have oodles of space on other data drives which is just not being used and even access to NAS drives.

Failing that, can I limit the size of the logfiles in some way so entries "fall off the end" when old enough?

Is it possible to manually close off and move the current logfiles to a different storage location and restart the logging procedure from scratch?

If there is any better way of dealing with this problem I would appreciate a heads up from those who know.  (I am technical so techspeak will not phase me, but I'm not a network manger or security specialist.)

 

EDIT:  Actually looking at the files in the Logs folder, there is only one which seems out of control.  hipslog.dat is almost the entire 65GB.  Even just dealing with that one would solve the problem.

Edited Tuesday at 11:18 AM by Bordonbert

[Bordonbert 0]

Hipslog.dat is growing as I watch.  It grows by about 5k per second constantly.

[Bordonbert 0]

Think I might have got to the root of the problem.  I have "Log all blocked operations" set.  I gather this should only be turned on when troubleshooting or when requested by support staff.  It's off now and the hips log has stopped growing.

Now to clean up the mess.  Is it safe to simply delete that hips logfile?  I have had no events for years that are major which I would have thought could be registered in there.

[Marcos 5,165]

8 minutes ago, Bordonbert said:

Now to clean up the mess.  Is it safe to simply delete that hips logfile?  I have had no events for years that are major which I would have thought could be registered in there.

It is safe to delete hipslog.dat in safe mode.

[Bordonbert 0]

Thanks for confirming that Marcos.  I'll go ahead and do it now.  All tidy and plenty of space on that drive.

[itman 1,720]

My guess here is you have enabled the Log all blocked operations setting in Eset HIPS Advanced Setup. Make sure its disabled per below screen shot;