Re: VB6 and antivira's
- From: "Twayne" <nodoby@xxxxxxxxxxxxxxxxxxx>
- Date: Wed, 12 Dec 2007 16:56:51 GMT
Mike Williams wrote:
"Johnny E. Jensen" <johnny@xxxxxxxxx> wrote in
message
news:OiPOLnKPIHA.2376@xxxxxxxxxxxxxxxxxxxxxxx
I found out that McAfee checks the InternalTrace.log
file each time it been written to.???? Other
Anviviras
don't perform this check. So to my quistion: Is
there a
way to prevent this check, from the way i writes to
the
logfile?
McAfee is notorious for slowing down machines,
something which you
often don't notice unless you have the misfortune to
use a slow old
fashioned machine that has a modern version of McAfee
installed. I
don't use McAfee myself any more, but I'm sure there
will be a way of
taming it in this specific respect. However, that
won't help you in
respect of your users' machines unless all of your
users do the same.
Looking at the way you are creating the log (at least
two entries
every time a function is used) I would imagine it can
get to quite a
size, so it might instead (and possibly as well) be a
good idea to
split your log file up into a number of much smaller
files (perhaps
starting a new file when the current file exceeds 10K
or so) so that
when McAfee (or anything else) checks the writes it
will have only a
small file to check, which should speed it up quite a
lot. Perhaps
mybiglog000001.log, mybiglog000002.log, etc. If you
ever want your
user to send you the logs for inspection then you
could ask them to
zip and send the entire set, or alternatively you
could build a small
facility built into your app that the user can select
which will
concatenate the log files for the user so that they
could send a
single large complete log to you. Anyway, something
along those lines
might be a good idea. I don't produce software for
sale and so I
don't often find the need for log files, so maybe
others here will
have a much better idea, but those are my initial
thoughts for what
they're worth.
Mike
I don't know about McAfee but I imagine it's similar to
Norton which I have experimented with a bit. The
largest delays seem to be in calling up the service and
then clearing it out; the scan itself appears to be
pretty fast relative to the call/clearing of the AV
scanner, especially where text is involved. Splitting
a huge file may of course help, but I think there is a
point of diminishing returns that might be approached
earlier than expected and not be as much help as hoped
for.
It's interesting that McAfee checks log files; they
must have maximized their scanning controls, or more
likely they're defaulted to scan everything that gets
created moved or saved in any way, which can slow down
the best of machines noticeably especially if coupled
with heirustic checks, which I think McAfee is capable
of and probably defaulted to do.
I think I'd try a different extension name than .log or
anything that currently exists, and see if the problem
persists. It might not, but ... then again ... if
McAfee is watching all disk & RAM write activity, well
.... .
This is probably no help, but I thought I'd toss in my
2 ¢ .
Pop`
.
- References:
- VB6 and antivira's
- From: Johnny E. Jensen
- Re: VB6 and antivira's
- From: Mike Williams
- VB6 and antivira's
- Prev by Date: Re: Is developing in VB6 still viable?
- Next by Date: Re: Form is truncated.....
- Previous by thread: Re: VB6 and antivira's
- Next by thread: MYSQL Help
- Index(es):
Relevant Pages
|
