Evan Knop wrote:
I have two usage scenarios here which may be accounted for; my
programming heritage is mostly Linux, but I've been pressed into work on
the Windows client, as I'm the only one currently at Thayer with
knowledge of both subject realms.
1) I have been using this mechanism to access AFS files for use by
"Scheduled tasks" as part of our account synchronization process. It's
nasty and ugly, and I'd love to replace parts of it, but it's also
better than nothing, and I don't have a lot of time to work on any of
it. Will the UNC paths work when there are no users logged in, assuming
that the path to the volume is readable by the machine (using IP-based
ACLs)?
UNC paths are the only thing that is guarrantee to be there.
If you are using the loopback adapter (as would be the case with 1.3.71)
then your AFS SMB/CIFS Service name is "AFS". Therefore, your UNC path
will be
\\AFS\<cellname>\<path>
\\AFS\all\<path>
\\AFS\<submount>\<path>
2) We have several computer labs using the latest OpenAFS client.
After the change in 1.3.65-66 (or thereabouts), we have started using
the "Global Drive" mapping to allow all our users (students, which
change every 10 weeks in some cases) to have a consistent drive
mapping. Is there a new recommended way of having this set up? If so,
what is it? I'm new enough to managing Windows that I have no idea how
this stuff works, and our Windows guys refuse to touch AFS, so I'm not
quite sure where to go.
The consistent path is the UNC path as described above.
Jeffrey Altman
smime.p7s
Description: S/MIME Cryptographic Signature
