Ticket #100 (new bugs)

Opened 12 years ago

Last modified 12 years ago

copy manager not maintaining all state of copied files

Reported by: patrick Owned by: tigran
Priority: major Milestone: 1.8.0-16
Component: utilities Keywords: copy manager
Cc: Sub Version:


We have been using the CopyManager to do some pool to pool copies, and it has been really helpful. We have noticed that when copying files, if the file was precious, the copied file has that state, but if the file was pinned the new file is not pinned. Taking into account that pinned is roughly equivalent to precious in the new semantics of the SRM 2.2, that is really dangeous (could get precious files removed). Is there any flag to force that the state of the file is the same when migrating? In the case there's none, isn't this a desirable feature to implement in further revisions? Seems fairly simple at first glance.

Change History

comment:1 Changed 12 years ago by patrick

  • Milestone changed from 1.8.0-15 to 1.8.0-16
Note: See TracTickets for help on using tickets.