From: "Schaible, Joerg" <Joerg.Schaible@gft.de>
To: cygwin@sources.redhat.com
Subject: WG: Cygwin .tar.gz files and anti-virus software
Date: Wed, 06 Sep 2000 04:09:00 -0000 [thread overview]
Message-ID: <C2D7D58DBFE9D111B0480060086E9635021D9D75@mail.gft.de> (raw)
[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #1: Type: text/plain, Size: 1621 bytes --]
-----Ursprüngliche Nachricht-----
Von: Schaible, Joerg
Gesendet am: Mittwoch, 6. September 2000 13:06
An: 'David Starks-Browning'
Betreff: AW: Cygwin .tar.gz files and anti-virus software
Had these problems with Norton AV and NT 4. I exclude the Cygwin root now to
have no problems.
-----Ursprüngliche Nachricht-----
Von: David Starks-Browning [ mailto:starksb@ebi.ac.uk ]
Gesendet am: Dienstag, 22. August 2000 22:08
An: cygwin@sources.redhat.com
Betreff: Cygwin .tar.gz files and anti-virus software
Greetings Cygwin devotees,
It is known that Network Associates (formerly McAfee) anti-virus
software can "hang" or otherwise behave poorly when dealing with
Cygwin .tar.gz files.
Has anyone experienced this problem with other anti-virus software?
(You needn't tell me that you use such-an-such and don't have a
problem. Or to confirm that you've had problems with McAfee. Just
report problems with other anti-virus scanners.)
Thanks very much.
Regards,
David
(Cygwin FAQ maintainer)
-------------------------------------------------------------------
David Starks-Browning | starksb@ebi.ac.uk
EMBL Outstation -- |
The European Bioinformatics Institute |
Wellcome Trust Genome Campus | tel: +44 (1223) 494 616
Hinxton, Cambridge, CB10 1SD, UK | fax: +44 (1223) 494 468
-------------------------------------------------------------------
--
Want to unsubscribe from this list?
Send a message to cygwin-unsubscribe@sourceware.cygnus.com
--
Want to unsubscribe from this list?
Send a message to cygwin-unsubscribe@sourceware.cygnus.com
reply other threads:[~2000-09-06 4:09 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=C2D7D58DBFE9D111B0480060086E9635021D9D75@mail.gft.de \
--to=joerg.schaible@gft.de \
--cc=cygwin@sources.redhat.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).