> You can provide your users with scripts to run to prioritize the client > for their current location.
Okay, not a problem, but I take it that means there is no public repository for scripts like these? >> >> The way I understand the volume access is that even if a volume is >> mounted R/W, its R/O vol is accessed until a write operation, in which >> case all further access (including reads) are from the R/W vol. If so, >> then a user should ideally be able to use the local server for most >> reads. > > There are two types of mount points: normal and read-write. If all of > the mount points are normal, then a readonly replica is preferred over a > read-write volume. If there is no readonly replica, then the readwrite > is used. In my experience, a volume that's not explicity mounted R/W is R/O under /afs/cell . So write access is only possible, then, through /afs/.cell and must be released before the result shows up under /afs/cell ? linux1:/afs/cell# kinit admin Password for ad...@cell: linux1:/afs/cell# aklog linux1:/afs/cell# tokens Tokens held by the Cache Manager: User's (AFS ID 1) tokens for a...@cell [Expires Jan 16 17:04] --End of list-- linux1:/afs/cell# fs lsm * 'test' is a mount point for volume '%test' 'ARCHIVE' is a mount point for volume '#archive' linux1:/afs/cell# fs listacl ARCHIVE Access list for ARCHIVE is Normal rights: system:administrators rlidwka linux1:/afs/cell# cd ARCHIVE linux1:/afs/cell/ARCHIVE# touch testfile touch: cannot touch `testfile': Read-only file system linux1:/afs/cell# cd ../test linux1:/afs/cell/test# fs listacl . Access list for . is Normal rights: system:administrators rlidwka system:authuser rl linux1:/afs/cell/test# touch testfile linux1:/afs/cell/test# ls -l testfile -rw-r--r-- 1 bin root 0 Jan 15 17:05 testfile So, maybe it's just a slight difference, but a not explicity-RW-mounted volume is effectively RO if the RO volume is available, right? So I can mount a volume "normally" and be accessing the RO vol for reads, but not then be able to write to the RW vol without changing the path to /afs/.cell . My concern is with how to best mount volumes, especially under the three scenarios listed in the original email (sfw repo, group dir, and user dir). >> The files regular users are concerned with are mostly documents, images, >> and presentations. Their heavy sharing is usually confined to a small >> set of small files (usually less that 1MB each); sets change as projects >> change (weekly/monthly). Still, it takes about 1 minute to transfer 1MB >> across the VPN -- not insignificant. > > What operating system? The clients run on linux 2.6, openbsd 4.4, windows xp sp3, and (forgot to mention before) max os 10.4. The users do their work from the mac and xp systems. -Chaz _______________________________________________ OpenAFS-info mailing list [email protected] https://lists.openafs.org/mailman/listinfo/openafs-info
