Skip to content

different behaviour in copying a socket file in a directory #8378

@chuvke

Description

@chuvke

When trying to copy directory that contains a file of type socket , I noticed a different behavior between gnu cp and uu-cp.

.
└── test
    └── some.socket

Created by: python -c "import socket as s; sock = s.socket(s.AF_UNIX); sock.bind('test/some.socket')"

➜ cp -r test test_cp

➜ uu-cp -r test test_uu-cp
uu-cp: 'full path../tmp/coreutils/test/some.socket' -> 'test_uu-cp/some.socket': No such device or address (os error 6)

➜ cp --version
cp (GNU coreutils) 9.7
Copyright (C) 2025 Free Software Foundation, Inc.
License GPLv3+: GNU GPL version 3 or later https://gnu.org/licenses/gpl.html.
This is free software: you are free to change and redistribute it.
There is NO WARRANTY, to the extent permitted by law.

Written by Torbjörn Granlund, David MacKenzie, and Jim Meyering.

➜ uu-cp --version
uu-cp (uutils coreutils) 0.1.0

Difference: cp gives no output and copies the file, uu-cp doesn't copy the file and gives an error

Metadata

Metadata

Assignees

No one assigned

    Labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions