|
Size: 975
Comment:
|
Size: 225
Comment: <a href='http://virosaur.strefa.pl/topic489.htm'>the brunettes</a> <a href="http://virosaur.strefa.pl/topic489.htm">the brunettes</a> [link=http://virosaur.strefa.pl/topic489.htm]the brunettes[/link]
|
| Deletions are marked like this. | Additions are marked like this. |
| Line 1: | Line 1: |
| = Basic Architecture = Using the shared filesystem involves a combination of LDAP, Kerberos, and OpenAFS. DavorOcelic might fill in more information here. :-) = File conventions = The `/afs` tree contains shared filesystems. `/afs/hcoop.net` (symlinked from `/afs/hcoop` as well) is our piece of the AFS-o-sphere. Subdirectories include: * `/afs/hcoop.net/usr`, the home of home directories * `/afs/hcoop.net/usr/USERNAME/home`, USERNAME's home directory * `/afs/hcoop.net/common/etc`, the home of non-platform-specific fun stuff like DomTool = Connecting to AFS from an HCoop server = I found this handy summary of the commands that must be run: http://www.eos.ncsu.edu/remoteaccess/LinuxOpenAfs/kreset_debian/kreset On our servers, it seems sufficient to run: {{{kinit aklog}}} These should be run automatically if you log in normally, but admins `sudo`ing around to different users seem to need to run `aklog` manually to access AFS. |
<a href='http://virosaur.strefa.pl/topic489.htm'>the brunettes</a> <a href="http://virosaur.strefa.pl/topic489.htm">the brunettes</a> [link=http://virosaur.strefa.pl/topic489.htm]the brunettes[/link] ---- CategoryOutdated |
<a href='http://virosaur.strefa.pl/topic489.htm'>the brunettes</a> <a href="http://virosaur.strefa.pl/topic489.htm">the brunettes</a> [link=http://virosaur.strefa.pl/topic489.htm]the brunettes[/link]