From: L A Walsh <cygwin@tlinx.org>
To: cygwin@cygwin.com
Subject: Re: find command seems to lock files
Date: Wed, 21 Aug 2019 19:53:00 -0000 [thread overview]
Message-ID: <5D5DA096.4050809@tlinx.org> (raw)
In-Reply-To: <1621839017.20190819194256@yandex.ru>
On 2019/08/19 09:42, Andrey Repin wrote:
> In regard to antivirus,
> 1. first make sure your local AV does not scan network directories by default.
> This is a gigantic usability issue for multiple reasons and normally is never done.
>
Except by microsoft, of course.
Microsoft's malware scanner (home essentials) scans network
drives as well as local by *default*. I had to make sure to list
any network drives in the exclusions section (which it seems to honor).
Sorta odd how their builtin OS 'search' command cannot index remote
drives**, but their virus scanner, by default, is able to do so.
**-can only use the remote server's index via its 'federated search
capability' which delegates the search of the remote file system to
the remote search program -- of course its only available on MS systems,
so indices of non-MS, network attached storage (NAS) isn't available.
--
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
next prev parent reply other threads:[~2019-08-21 19:50 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-08-19 12:49 Morten Kjærulff
2019-08-19 14:06 ` Corinna Vinschen
2019-08-19 14:13 ` Eliot Moss
2019-08-19 14:26 ` Corinna Vinschen
2019-08-19 14:41 ` Morten Kjærulff
2019-08-19 15:03 ` Eliot Moss
2019-08-19 17:05 ` Andrey Repin
2019-08-19 17:21 ` Andrey Repin
2019-08-19 17:41 ` Morten Kjærulff
2019-08-19 18:52 ` Eliot Moss
2019-08-19 19:43 ` Greywolf
2019-08-21 19:53 ` L A Walsh [this message]
2019-08-26 1:57 ` Chris Wagner
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=5D5DA096.4050809@tlinx.org \
--to=cygwin@tlinx.org \
--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).