>>>>> "John" == John Sopko <[EMAIL PROTECTED]> writes:
John> That is why it is important to have your volume names match the
John> point at which it will be mounted. For example our home
John> directory volumes are named "home.username" the mount point is
John> "/afs/sitename/home/username", are projects are mounted at
John> "/afs/sitename/project/projectname" with a volume name of
John> "project.projectname". I think there is a 32 character volume
John> name limit. This is a good way to keep track where a volumes
John> mount point should be.
No, its a 22 character limit and mapping the pathname into the volume
name won't scale.
Besides, you still need an audit to enforse the policy you choose.
Just because the naming convention implies a certain mount point,
there is no guarantee that other, unofficial mount points don't exist
(since the creation of a mount point requires nothing other than
insert permission in any given directory, not special administrator
priveledge).
Likewise, you can't be guaranteed the original mount is still there.
This type of audit is pretty critical for maintaining sanity in a
large AFS cell.
Phil
