Re: Weird behavior with find command when tarring files

From: Stefan Knecht <knecht.stefan_at_gmail.com>
Date: Fri, 19 Oct 2018 13:29:15 +0700
Message-ID: <CAP50yQ-6D2PYg036hrvcr2BiH+nHw5KQe6fyL81rBA-Gheb9LA_at_mail.gmail.com>



Use tar -r instead of tar -c

It will create the archive if it doesn't exist and append to it if it does. Your call to tar -c will probably overwrite the file each time it runs.

On Fri, Oct 19, 2018 at 3:58 AM Hameed, Amir <Amir.Hameed_at_xerox.com> wrote:

> Hi,
>
> I am using the *find* command to TAR up files that are older than 4 hours:
>
>
>
> find . type f -mmin +239 | xargs tar -cvf /tmp/test.tar
>
>
>
> The command tars up files and seems to finish fine. However, when I untar
> and count the number of files against the count of files that should have
> been captured (find . type f –mmin +239 | xargs ls –l | wc -l) there is a
> huge difference and the files captured by tar were way less than the file
> listed for the same time.
>
>
>
> This is a strange behavior. What am I doing wrong (I am sure I am doing
> something wrong)?
>
>
>
>
>
> Thanks,
>
> Amir
>
>
>
>
>

-- 
//
zztat - The Next-Gen Oracle Performance Monitoring and Reaction Framework!
Visit us at zztat.net | _at_zztat_oracle | fb.me/zztat | zztat.net/blog/

--
http://www.freelists.org/webpage/oracle-l
Received on Fri Oct 19 2018 - 08:29:15 CEST

Original text of this message