Hello Roberto,

Is it possible to open logfiles NON exclusevely for reading, but exclusevely for writing of course (as it does MS IIS, for example) so it will be possible to view it in real time by compatible viewers (I usually use FAR Manager for fast troubleshouting/monitoring)?

Thank you.

Roberto,

As I can see, SpamFilter opens logfile every 60 seconds, writes to it, and closes again. Therefore I can open this file for reading AND even for writing in this period. So when spamfilter tries to reopen it again - it can't place lock for writing and drops error in realtime logmonitor window.

Instead of Spamfilter IIS (as mentioned above) opens logfiles exclusively for writing, but do not block reading (may be not for writing, but "append", I don't remember the certain attributes in fopen() ). IIS don't close the file until it stops. So I can not open it for writing (while IIS works), but I can copy it and I can view it without preventing IIS to access the file. In fact I can even see how new lines are added to it in realtime without reopening the file.

I think, as long as Spamfilter does not need to read the logfile itself or write in voluntary position, it is enough to open logfile in "append" mode and do not close it while application runs. It's only a matter of changing attribute in fopen() and open-close-reopen-... sequence.

Edited by Roman