Date: Tue, 26 Apr 2016 15:23:24 +0100 From: Arthur Chance <freebsd@qeng-ho.org> To: David Banning <david+dated+1462111984.5033c3@skytracker.ca>, Michael Schuster <michaelsprivate@gmail.com> Cc: questions@freebsd.org Subject: Re: deleting /tmp files from crontab Message-ID: <c4cc62e8-3065-8175-f6ac-7375524a38f0@qeng-ho.org> In-Reply-To: <20160426141301.GA62352@skytracker.ca> References: <20160426123012.GA57555@skytracker.ca> <571F63B3.4040803@gmail.com> <20160426141301.GA62352@skytracker.ca>
next in thread | previous in thread | raw e-mail | index | archive | help
On 26/04/2016 15:13, David Banning wrote:
> On Tue, Apr 26, 2016 at 02:48:51PM +0200, Michael Schuster wrote:
>> On 26/04/16 14:30, David Banning wrote:
>>> I am attempting to delete my .spamassassin files from my /tmp directory
>>>
>>> putting a command in my crontab;
>>>
>>> find /tmp/.spam* -mmin +360 -delete
>>
>> the find syntax looks strange (assuming this is straight 'find', not
>> somthing crontab-specific); normally, I'd expect to see
>>
>> # find /tmp -name '.spam*' -mmin +360 -delete
>
> That seems to delete the files, but not the directories starting in .spam*
>
> Reviewing the find man page, it appears the -delete implementation will
> not work unless the directory is empty. Still looking for solutions here.
Take a look at the -d or argument-less -depth primaries. From the man page
-depth Always true; same as the non-portable -d option. Cause find to
perform a depth-first traversal, i.e., directories are visited in
post-order and all entries in a directory will be acted on before
the directory itself.
--
Moore's Law of Mad Science: Every eighteen months, the minimum IQ
necessary to destroy the world drops by one point.
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?c4cc62e8-3065-8175-f6ac-7375524a38f0>