[tahoe-dev] [tahoe-lafs] #849: Tahoe cp command refuses to copy remote files to /tmp

tahoe-lafs trac at allmydata.org
Sat Dec 5 20:31:42 PST 2009


#849: Tahoe cp command refuses to copy remote files to /tmp
-------------------------------+--------------------------------------------
 Reporter:  AgentME            |           Owner:           
     Type:  defect             |          Status:  new      
 Priority:  minor              |       Milestone:  undecided
Component:  code-frontend-cli  |         Version:  1.5.0    
 Keywords:                     |   Launchpad_bug:           
-------------------------------+--------------------------------------------

Comment(by AgentME):

 Replying to [ticket:849 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.

-- 
Ticket URL: <http://allmydata.org/trac/tahoe/ticket/849#comment:1>
tahoe-lafs <http://allmydata.org>
secure decentralized file storage grid


More information about the tahoe-dev mailing list