Richard,
It turns out that I was confused in general and by the confusing
documentation :) Attempting the tests you describe below work as you have
suggested. Some of the symlinks I was trying to back up were pointing to
unavailable cells in AFS. The errors I was getting were just stat() calls
that were failing. Unfortunately I believed the documentation without doing
much research. I won't make that mistake again.
Jerome
--On 10/26/00 10:11:38 -0400 [EMAIL PROTECTED] wrote:
>> I want to use the subdir=y option to backup all of the subdirs
>> interactively. However, I don't want to follow symlinks. Looking at the
>> documentation, there seems to be no way to do this as specifying
>> -subdir=y also follows symlinks. Am I missing something obvious?
>
> Jerome - I think the documentation is a bit confused, which in turn
> makes its readers confused. I think that what it means to
> say is that the subdir=y will incidentally cause files and directories
> under the backup-specified directory to be backed up. I just tried an
> experiment under a 3.7.2 client, creating symlink /a/b/syml which
> points to /a/d/target, and then did 'dsmc i -su=yes /a/b/\*' :
> this caused the /a/b/syml to be backed up, but not the /a/d/target,
> though it is in the same file system (/a).
> If anyone sees contrary behavior from other client levels, it
> would be worth posting and pondering.
> Richard Sims, BU
