On 24 Jan 2006, at 1:04 am, John Gruenenfelder wrote:
Oh, I should have made that a little more clear. The machine in
question is
not actually using the amd.home map. The other two machines in the
cluster
use it. I just included it for completeness. On this particular
machine,
/home is local so there is no need for a map.
But, to insure that some file is accessible on all machines through
the same
path, we often use things like /net/bach/d1/foo even when on
machine bach.
That way the path doesn't change if accessed from another machine.
Right - I'm doing something similar here, although a slightly
different way.
There have been some reports on the am-utils mailing list about
problems with the link mount type on debian; you were the first but
you're not the only one. There may be a bug, but no-one's managed to
identify it yet. I have just uploaded the latest stable version
(6.1.5) to debian unstable. You'll have to wait for the AMD64
autobuilder to do its thing, so it may take a day or two to appear.
I'd appreciate it if you could have a look at it and see if the
problem is still there. If it is, then we'll have to get some more
debugging information to the am-utils developers.
Tim
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
