[prev in list] [next in list] [prev in thread] [next in thread] 

List:       kde-bugs-dist
Subject:    [Baloo] [Bug 331932] add option for disabling indexing
From:       <sludtke42 () gmail ! com>
Date:       2014-05-04 17:23:07
Message-ID: bug-331932-17878-Tj3VxMjnFd () http ! bugs ! kde ! org/
[Download RAW message or body]

https://bugs.kde.org/show_bug.cgi?id=331932

--- Comment #47 from sludtke42@gmail.com ---
Yes, but shred should never happen automatically! On some drive types (SSDs),
shred does not work properly, and can dramatically reduce the lifespan of the
drive.

----------------------------------------------------------------------------
Steven Ludtke, Ph.D.
Professor, Dept of Biochemistry and Mol. Biol.         (www.bcm.edu/biochem)
Co-Director National Center For Macromolecular Imaging        (ncmi.bcm.edu)
Co-Director CIBR Center                          (www.bcm.edu/research/cibr)
Baylor College of Medicine                             
sludtke@bcm.edu





On May 4, 2014, at 12:09 PM, Grósz Dániel <groszdanireg@gmail.com> wrote:

> https://bugs.kde.org/show_bug.cgi?id=331932
> 
> --- Comment #46 from Grósz Dániel <groszdanireg@gmail.com> ---
> (In reply to comment #45)
>> I have seen that the baloo author stated that in 4.13.x that when baloo has
>> $HOME included in the avoid list then it will simply delete the associated
>> database files that have been created without the user's explicit authority,
> 
> For security reasons that should be with "shred". Otherwise it makes the
> security problem worse: the user is not even left with an option to shred the
> database after adding $HOME.
> 
> On a side note: why add $HOME to disable, and not / ? Also, if adding $HOME
> disables everything, how does the user (who likes Baloo) add directories
> outside of $HOME?
> 
> -- 
> You are receiving this mail because:
> You are on the CC list for the bug.

-- 
You are receiving this mail because:
You are watching all bug changes.=
[prev in list] [next in list] [prev in thread] [next in thread]