Tahoe cp command refuses to copy remote files to a local directory that contains special files

[AgentME]

( test: is set to URI:DIR2-RO:5vpbdqwe7wu5ch3u6r6qeuldle:5lsoilnoaa2rmtk7dbkukrirazs2eayzdohyj3kkbjj4tinquvnq )

On my Ubuntu system, this command fails:

tahoe cp -r test:blah/file.txt test:blah/file2.txt /tmp/

I've attached the error it gives to this post to save space.

However, running this following command works fine, whether or not the directory "aaa" already exists:

tahoe cp -r test:blah/file.txt test:blah/file2.txt /tmp/aaa/

[AgentME]

Replying to AgentME:

( test: is set to URI:DIR2-RO:5vpbdqwe7wu5ch3u6r6qeuldle:5lsoilnoaa2rmtk7dbkukrirazs2eayzdohyj3kkbjj4tinquvnq )

This example is on the test grid by the way, though I figure that would be most people's first guess. Nothing special about the files besides them being only a few bytes for a quick download.

I made a copy of /tmp and tried to figure out what was special about it that tahoe cp choked on it for. I finally found out that it was because of the sockets located in that folder. After I removed the sockets from the copy of /tmp, I was able to use tahoe cp to make files in that folder.

It seems that if there's an object in a folder that isn't a file, directory, or symlink, (like a fifo pipe or socket) then "tahoe cp -r" will crash when you try to write files to that directory.