Thanks!
I didn't realize the unix client didn't allow bidirectional linkage (docs
for linked cells are hard to find).
Anyway, I have gotten this to work now but I had to use the reverse order
that you suggested.
newcell oldcell #name
oldcell #name
Otherwise I still got the original error 2.
Cheers,
Stephen
On Mon, 12 Aug 2013, Derrick Brashear wrote:
the unix client will not allow bidirectional linkage, and you must name the
cell being linked to before the
cell linking to it, in order, in the CSDB.
e.g.
oldcell #whatever
newcell oldcell #whatever.
On Mon, Aug 12, 2013 at 5:45 PM, <[email protected]> wrote:
Hi,
Any known bugs in the parsing of CellServDB syntax for linked cells? I
ask because I seem to be
experiencing one and am trying to determine if it's a known problem or
PEBKAC (problem existing
between keyboard and chair).
I'm trying linked cells as per the docs I found at
<http://docs.openafs.org/ReleaseNotesWindows/Linked_Cells.html>. Upon
starting the client, I get
the following messages.
Starting AFS services: openafs afsd.
Adding cell 'oldcell.unc.edu': error 2
Adding cell 'newcell.unc.edu': error 2
afsd: All AFS daemons started.
Client is "Linux tasty 3.2.0-51-generic #77-Ubuntu SMP Wed Jul 24
20:18:19 UTC 2013 x86_64
x86_64 x86_64 GNU/Linux"
Openafs version is 1.6.1+ubuntu0.2 -- just 'cuz that's the newest in the
repo.
Here's the syntax I've tried:
newcell.unc.edu oldcell.unc.edu #New Cell
152.2.4.5 #afsdb1.newcell.unc.edu
152.2.5.6 #afsdb2.newcell.unc.edu
152.2.6.7 #afsdb3.newcell.unc.edu
oldcell.unc.edu newcell.unc.edu #Old Cell
152.2.1.2 #db1.oldcell.unc.edu
152.2.2.3 #db1.oldcell.unc.edu
152.2.3.4 #db1.oldcell.unc.edu
Interestingly, I can configure linked cells correctly via "fs newcell
-linkedcell". So, is this
something obvious I'm doing wrong or should I open a bug report?
Cheers,
Stephen
_______________________________________________
OpenAFS-info mailing list
[email protected]
https://lists.openafs.org/mailman/listinfo/openafs-info
--
Derrick
