[7482] in SIPB bug reports
Re: sipb.mit.edu to athena.mit.edu synctree errors
daemon@ATHENA.MIT.EDU (Jacob Morzinski)
Mon Jan 17 04:52:19 2000
Date: Mon, 17 Jan 2000 04:52:07 -0500 (EST)
From: Jacob Morzinski <jmorzins@MIT.EDU>
To: sipb-afsreq@MIT.EDU
Cc: bug-sipb@MIT.EDU
In-Reply-To: <Pine.LNX.4.21.0001161559000.4015-100000@well.mit.edu>
Message-Id: <Pine.GSO.4.21.0001170446001.11986-100000@home-on-the-dome.mit.edu>
Mime-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
On Sun, 16 Jan 2000, Jacob Morzinski wrote:
> My fault -- I put a .rconf file into a tree that had already been
> synctreed into the athena cell. I removed the athena cell copy
> of the affected directory; hopefully this will cause it to be
> synctree'd from scratch.
Perhaps someone can help me with a question. What's the purpose
of the athena-cell copy of the sipb locker? The reason I
put a .rconf file in my pine source tree is to let me make
build trees on the local machine quickly. Now, though, the same
.rconf file has caused the athena cell copy of the pine source
tree to be a symlink farm pointing back to sipb cell. This
wouldn't be very useful, if the sipb cell was unavailable.
Granted, temporarily losing the pine source tree is not a big
deal. Still, is obeying .rconf files a known bug/feature?
-Jacob
