Coda File System

*** Not bound *** in hoard walk

From: Stephen J. Turnbull <>
Date: Tue, 18 Apr 2000 16:26:16 +0900 (JST)
>>>>> "Jan" == Jan Harkes <> writes:

    >> I didn't see an error at the time, but I've noticed since an
    >> occasional
    >> *** Not bound *** /coda/service/unique/director/etc d+
    >> after 'hoard walk'.

    Jan> Most likely a symlink, the fix for that one is already in
    Jan> CVS.

I've seen this, they were definitely symlinks for me.  However, the
hoard walk did not complete (files were missing, but I'm pretty sure
my network was flakey at the time; I don't recall the messages).
Rerunning the hoard walk patched most of them up (ie, there were no
messages), except that the message continued in one case where I
_know_ the symlink is dangling (in the source directory which I "cp
--archive'd" to /coda).

Is that correct?  If not, what is the desired behavior?

University of Tsukuba                Tennodai 1-1-1 Tsukuba 305-8573 JAPAN
Institute of Policy and Planning Sciences       Tel/fax: +81 (298) 53-5091
_________________  _________________  _________________  _________________
What are those straight lines for?  "XEmacs rules."
Received on 2000-04-18 03:28:43