From: "Michael Kairys" <kairys@comcast.net>
To: cygwin@cygwin.com
Subject: Re: BitDefender again
Date: Thu, 10 Sep 2009 12:04:00 -0000 [thread overview]
Message-ID: <h8apvr$fhi$1@ger.gmane.org> (raw)
In-Reply-To: <h7p5j8$p39$1@ger.gmane.org>
> But can anyone say more about Dave Korn's comment that it could "horribly
> frag your heap and bork
> your maximum allocatable memory limit"? Can I test this somehow?
Guess I'll just go with it then... :)
In the interim I've tried out a few other "leading" AV products: Avria,
Nod32, and Kaspersky, and I must say BitDefender is still my first choice.
My criteria are pretty simplistic though: score well in at least two
independent tests and otherwise be as invisible and unobtrusive as possible.
--
Problem reports: http://cygwin.com/problems.html
FAQ: http://cygwin.com/faq/
Documentation: http://cygwin.com/docs.html
Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple
prev parent reply other threads:[~2009-09-10 12:04 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-08-26 0:10 Michael Kairys
2009-08-26 1:36 ` Christopher Faylor
2009-08-26 11:37 ` Dave Korn
2009-08-26 13:19 ` Michael Kairys
2009-08-26 15:29 ` Wilfried
2009-08-27 13:19 ` Michael Kairys
2009-08-28 15:05 ` Wilfried
2009-08-29 2:08 ` Joe Smith
2009-09-01 13:28 ` Michael Kairys
2009-09-03 19:32 ` Michael Kairys
2009-09-10 12:04 ` Michael Kairys [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to='h8apvr$fhi$1@ger.gmane.org' \
--to=kairys@comcast.net \
--cc=cygwin@cygwin.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).