cp -a *.socket generates wrong error
Open
Nobody has claimed this yet.
U - cp
- Dominant language
- Rust
- Stars
- 24.1k
- Forks
- 2k
- Avg merge
- 1d 5h
- Merged PRs (30d)
- 365
Description
$ cp -a /run/dbus/system_bus_socket /tmp/s
cp: No such device or address (os error 6)
$ '/home/a/bin/gnu9.11/cp' -a /run/dbus/system_bus_socket /tmp/s # success
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start with the Rust implementation of the cp command and reproduce the reported command using /run/dbus/system_bus_socket and /tmp/s. Compare its behavior and error with the successful GNU coreutils invocation; done means cp -a handles this socket consistently without the reported error.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- rust
- Domain
- cli
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Quiet
- Clarity
- Mostly clear
- Newbie friendliness
- 55/100