Jeffrey:
I'm still having problems with this; I tried your daily build from 9/23,
however the AFS service would not even start for me with that build.
I have backed down to the 1.3.7100 release and the service starts normally
again.
What I'm trying to do is store windows roaming profiles in AFS.
The problem turned out to be non-existant "IBM\AFS\etc." directories
in the PATH environmental variable on my laptop. When I removed them
and restarted the computer, the OpenAFS 1.3.71 client worked.
I don't know how those PATH entries got there. Perhaps the installer
for the earlier version of
Sorry I missed that. I added the contents of the PATH to the
afsd_init.log specifically so that mixed installations of OpenAFS
and IBM/Transarc AFS on Windows could be detected.
This PATH entry was not created by OpenAFS; it was created by the
installation of IBM/Transarc AFS on the machine.
Jef
Stephen Joyce wrote:
C:>dir u:
The system canot find message text for message number 0x13d in the message
file for System.
Interestingly, the dir of \\winho-afs\users SUCCEEDED the very first time I
executed the command, but failed thereafter. This is not a tokens issue;
the same user can issue t
This is a personal machine. The interest in OpenAFS was its price.
IBM/Transarc AFS was out of my price range--particularly since my use
of AFS is work related. Having work pay for it on this machine was an
argument I didn't think would succeed, or be justifiable. When work
switched to OpenAFS f
There is no IBM path information in the 1.3.xx installers for
OpenAFS. We completely replaced the installer from scratch.
Did you install the older 1.2.xx version of OpenAFS on your machine?
If so, that is most likely where it came from.
Jeffrey Altman
Alan Wehmann wrote:
This is a personal machi
John W. Sopko Jr. wrote:
Try turning off the "-dynroot" option to afsd, if dynroot is on you cannot
access root.afs. I think it best to keep this off on my AFS servers.
you should be able to create a mount point for root.afs within your
dynamic root.
fs mkmount /afs/myroot.afs root.afs cell.nam
On Mon, 27 Sep 2004, Jeffrey Altman wrote:
John W. Sopko Jr. wrote:
Try turning off the "-dynroot" option to afsd, if dynroot is on you cannot
access root.afs. I think it best to keep this off on my AFS servers.
you should be able to create a mount point for root.afs within your dynamic
root.
like
I might have installed an older version, in the first place. The
first version that I installed was on a CD given to me by the person
who supports my desktop PC at work. I'll look for the CD and check.
Perhaps I never installed 1.3.64, before I installed 1.3.70 and later
1.3.71. I had the 1.3.64
