Okay, thanks.  That makes sense.  We're actually looking to err on the side of 
preserving the symlinks so that's convenient.

> On Mar 6, 2018, at 1:42 AM, LEIBOVICI Thomas <thomas.leibov...@cea.fr> wrote:
> 
> On 02/27/18 23:31, John White wrote:
>> I can’t seem to find any mention of this in the v3 admin docs - Does a 
>> cleanup run focusing solely on atime (condition { last_access > 365d }) 
>> ignore symlinks or will they be purge candidates?
>> ------------------------------------------------------------------------------
>> Check out the vibrant tech community on one of the world's most
>> engaging tech sites, Slashdot.org! http://sdm.link/slashdot
>> _______________________________________________
>> robinhood-support mailing list
>> robinhood-support@lists.sourceforge.net
>> https://lists.sourceforge.net/lists/listinfo/robinhood-support
> 
> The ploblem with symlink's "atime" is it is refreshed each time you read the 
> symlink, e.g. when running "ls -l" in the directory where it is located, or 
> even when robinhood scans it, etc...
> 
> So for symlink policies I suggest you rather use mtime (last_mod > 365d).
> 
> Regards,
> 
> Thomas
> 


------------------------------------------------------------------------------
Check out the vibrant tech community on one of the world's most
engaging tech sites, Slashdot.org! http://sdm.link/slashdot
_______________________________________________
robinhood-support mailing list
robinhood-support@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/robinhood-support

Reply via email to