On 10/28/98 17:49:05 you wrote:
NOW BEWARE! Once you test a few times and discover that ndmpcopy tends to hang, you can get into the habit of just interrupting it whenever you see that message. DON'T. If you are copying a very large amount of data, the restore will probably finish well after the dump. This is because the restore does a final pass (after all data has transferred) to set the correct owner and permissions on all directories. If you interrupt ndmpcopy while this is going on, you are left with a bunch of dirs owned by root, with permissions 777 on the restore filer. Can you guess how I found this out?? :-)
This should be entered as a bug. Even though interrupting a restore isn't something you should do, having it create potential security issues as a result isn't really necessary. It's probably nice to have that as a with ndmpcopy as a shortcut in the code (you can probably rely letting the requests go through a higher level, since they have "permission"), though, so it's not surprising it's there. May not be something that can be fixed easily.
Bruce