Scratch purging policy: Difference between revisions

Scratch purging policy (view source)

37 bytes removed , 6 years ago

Bureaucrats, cc_docs_admin, cc_staff

2,320

edits

Revision as of 17:26, 18 December 2017 (view source) Stubbsda (talk \| contribs) (Initial iteration of a page on scratch purging policy)		Revision as of 16:06, 12 January 2018 (view source) Stubbsda (talk \| contribs) (→‎Abuse) Newer edit →
Line 20:		Line 20:

	=Abuse=		=Abuse=
	It should be noted that this method of tracking file age does allow for potential abuse the system by periodically running a recursive <tt>touch</tt> command on your files, preventing them from being flagged for expiration. However the ~~use of this method is noticeable through periodic checks~~ and users ~~with large numbers of files which all have identical ages repeatedly showing up as expiration candidates~~ will be contacted and asked to modify their behaviour, in particular to move the "retouched" data from scratch to a more appropriate location.		It should be noted that this method of tracking file age does allow for potential abuse the system by periodically running a recursive <tt>touch</tt> command on your files, preventing them from being flagged for expiration. However Compute Canada staff have methods for detecting this and similar tactics to defeat the purging policy and users who employ such techniques will be contacted and asked to modify their behaviour, in particular to move the "retouched" data from scratch to a more appropriate location.