Path: csiph.com!aioe.org!.POSTED!not-for-mail From: Robert Peirce Newsgroups: comp.sys.mac.apps Subject: Re: tar: Pathname too long Date: Tue, 11 Oct 2016 13:07:27 -0400 Organization: Aioe.org NNTP Server Lines: 20 Message-ID: References: NNTP-Posting-Host: xT/KFuEPIyjBSSH8nb6GOA.user.gioia.aioe.org Mime-Version: 1.0 Content-Type: text/plain; charset=utf-8; format=flowed Content-Transfer-Encoding: 7bit X-Complaints-To: abuse@aioe.org User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.11; rv:45.0) Gecko/20100101 Thunderbird/45.3.0 X-Notice: Filtered by postfilter v. 0.8.2 Xref: csiph.com comp.sys.mac.apps:36870 On 10/5/16 7:35 PM, Robert Peirce wrote: > Got this from Google. > > This construct produces the usual error: > > find ./$i -newer TS -type f -print0 | tar --null -n -rf ~/pictures.t -T - > > This one doesn't except after building the correct file it ends by > deleting it contents: > > find ./$i -newer TS -type f -print0 | tar --null -n -cf ~/pictures.t -T - I was hoping somebody might be able to explain what is going on here. The -r flag produces the file name too long error. The -c flag does not but it deletes the file on completion. As near as I could tell before deletion, the two files were the same. So, is there a way to prevent -c from deleting the file?