How to avoid 'are the same file' warning message when using cp in Linux?

Question

I'm trying to copy certain files from one directory to another. Using this command

find "$HOME" -name '*.txt' -type f -print0 | xargs -0 cp -t $HOME/newdir

I get an warning message saying

cp: '/home/me/newdir/logfile.txt' and '/home/me/newdir/logfile.txt' are the same file

How to avoid this warning message?

Yes, this works but not quite the solution I was looking for :-) With this I get a rid of this warning but cannot avoid it still — Matkrupp, Aug 09 '13 at 19:27

score 24 · Accepted Answer · answered Aug 09 '13 at 19:17

24

The problem is that you try to copy a file to itself. You can avoid it by excluding the destination directory from the results of the find command like this:

find "$HOME" -name '*.txt' -type f -not -path "$HOME/newdir/*" -print0 | xargs -0 cp -t "$HOME/newdir"

answered Aug 09 '13 at 19:17

user000001

32,226
12
81
108

1

Thanks but this generates the same warning in Ubuntu. – Matkrupp Aug 09 '13 at 19:21

score 2 · Answer 2 · answered Mar 08 '20 at 17:21

2

try using install instead, this replaces by removing the file first.

install -v target/release/dynnsd-client target/
removed 'target/dynnsd-client'
'target/release/dynnsd-client' -> 'target/dynnsd-client'

and then remove the source files

answered Mar 08 '20 at 17:21

teknopaul

6,505
2
30
24

score 1 · Answer 3 · edited Apr 22 '14 at 23:39

1

Make it unique in the process. But this require sorting

find "$HOME" -name '*.txt' -type f -print0 | sort -zu | xargs -0 cp -t "$HOME/newdir"

Or if it's not about the generated files, try to use the -u option of cp.

find "$HOME" -name '*.txt' -type f -print0 | xargs -0 cp -ut "$HOME/newdir"

-u   copy only when the SOURCE file is newer than the destination file or when
     the destination file is missing

edited Apr 22 '14 at 23:39

Zombo

1
62
391
407

answered Aug 09 '13 at 19:11

konsolebox

72,135
12
99
105

Thanks, but both of these solutions generate the same warning message in Ubuntu bash. – Matkrupp Aug 09 '13 at 19:22

score 1 · Answer 4 · answered Jul 11 '20 at 08:48

install

worked perfectly in a Makefile context with docker - thanks!

copy:  
    @echo ''  
    bash -c 'install -v ./docker/shell                   .'  
    bash -c 'install -v ./docker/docker-compose.yml      .'  
    bash -c 'install -v ./docker/statoshi                .'  
    bash -c 'install -v ./docker/gui                     .'  
    bash -c 'install -v ./docker/$(DOCKERFILE)   .'  
    bash -c 'install -v ./docker/$(DOCKERFILE_SLIM)        .'  
    bash -c 'install -v ./docker/$(DOCKERFILE_GUI)         .'   
    bash -c 'install -v ./docker/$(DOCKERFILE_EXTRACT) .'  
    @echo ''  

build-shell: copy  
    docker-compose build shell

Daniel Rijsketic · Answer 5 · 2022-05-25T21:00:20.367

1

Try using rsync instead of cp:

find "$HOME" -name "*.txt" -exec rsync {} "$HOME"/newdir \;

edited May 25 '22 at 21:00

answered May 25 '22 at 20:55

Daniel Rijsketic

11
2

rsync worked, nice! – abc Jul 11 '23 at 21:37

How to avoid 'are the same file' warning message when using cp in Linux?

5 Answers5