You can disable .DS_STORE creation on network filesystems, which
should ease some of the stress. You can also outright disable the
indexer or tell it places not to do it.
James
On Oct 15, 2008, at 10:00 AM, Bob Friesenhahn wrote:
> On Wed, 15 Oct 2008, Harry Lu wrote:
>>
>> Yes, it will index your home directory by default when it is started.
>> After the index is finished, it will idle until files
>> added/removed/modified in your home directory.
>
> How does it know if files are added/removed/modified in the user's
> home directory?
>
> What is the behavior like if the home directory is accessed over a
> network?
>
> What is the behavior like if the user is logged into 10 machines at
> once which share the same home directory?
>
> Is this somehow superior to the Mac DOS ("Denial Of Service")
> "mdworker" implementation or will Solaris finally catch up to the Mac
> in its ability to destroy the network and servers as well as local CPU
> and disk bandwith? On the Mac I often find that OS-X's indexing
> service consumes massive resources during bulk file copies.
>
> Bob
> ======================================
> Bob Friesenhahn
> bfriesen at simple.dallas.tx.us, http://www.simplesystems.org/users/bfriesen/
> GraphicsMagick Maintainer, http://www.GraphicsMagick.org/
>
> _______________________________________________
> desktop-discuss mailing list
> desktop-discuss at opensolaris.org
