|
Size: 4045
Comment: cat, update for dkms
|
Size: 1839
Comment: simplify and update for wheezy
|
| Deletions are marked like this. | Additions are marked like this. |
| Line 6: | Line 6: |
| These instructions have been tested on Debian wheezy. |
|
| Line 8: | Line 10: |
| == OpenAFS Client Installation == | |
| Line 9: | Line 12: |
| = OpenAFS Client Installation = {{{ aptitude install openafs-client }}} Answer the configuration questions as follows: |
To install the OpenAFS client and related programs, run `apt-get install openafs-client openafs-krb5 krb5-user` as root. Answer the configuration questions as follows: |
| Line 18: | Line 15: |
| * The default value for "Size of AFS cache in kB" is okay. You can increase the cache size if you want. * Dynamically generate the contents of /afs? Yes * DB server host names for your home cell: `afs.hcoop.net` * Run Openafs client now and at boot? Yes You may need to run `dpkg-reconfigure openafs-client` to get asked all of these questions. |
* Default Kerberos version 5 realm: `HCOOP.NET` |
| Line 24: | Line 17: |
| = Kernel Module Installation = | You can accept the default values for other questions. If you're not prompted for these values, run `dpkg-reconfigure -phigh openafs-client krb5-user`. |
| Line 26: | Line 19: |
| OpenAFS requires a kernel module. Debian kernels use DKMS, so installation of the package should automatically build and load the modules: | == Using AFS == |
| Line 28: | Line 21: |
| {{{ aptitude install openafs-modules-dkms }}} |
To gain access to your HCoop AFS share, run `kinit user@HCOOP.NET && aklog hcoop.net` on your local system. |
| Line 32: | Line 23: |
| OpenAFS's cache is located at /var/cache/openafs, and it must be on an ext2, ext3 or ext4 filesystem. If /var/cache is not on an ext2, ext3 or ext4 filesystem, you'll need to mount an ext2, ext3 or ext4 filesystem at /var/cache/openafs. OpenAFS cache does not work well, if at all, on ReiserFS systems. Restart OpenAFS: {{{ /etc/init.d/openafs-client restart }}} Now you should be able to see files in /afs/hcoop.net, but you won't have any AFS tokens. So let's install some Kerberos packages. = Kerberos Installation = {{{ aptitude install openafs-krb5 krb5-user }}} {{{#!wiki note You may not need to set anything other than the default realm--everything else should be fetched automatically through DNS. It does not, however, hurt to hard code these settings since they are unlikely to ever change. }}} * Default Kerberos version 5 realm: `HCOOP.NET` * Kerberos servers for your realm: `kerberos.hcoop.net` * Administrative server for your Kerberos realm: `kerberos.hcoop.net` If you are using Ubuntu Hardy, you might also need to add the following to your {{{/etc/krb5.conf}}} file, in the {{{[domain_realm]}}} section. It gets rid of a pesky warning. {{{ hcoop.net = HCOOP.NET .hcoop.net = HCOOP.NET }}} On Debian unstable, you may need to add `allow_weak_crypto = true` to the libdefaults section of `/etc/krb5.conf`. = Using AFS = Typically, to gain access to your HCoop AFS share, do the following on your local system: {{{ kinit user@HCOOP.NET aklog -c hcoop.net }}} Be sure that the `openafs` module is loaded or there will be errors. The tickets gained will last up to 10 hours but can be renewed with `krenew` for up to 8 days. Here's a common use: |
The tickets gained will last up to 10 hours but can be renewed with `krenew` for up to 8 days. Here's a common use: |
| Line 81: | Line 31: |
| = Troubleshooting = == ReiserFS == First, if you are using ReiserFS, the AFS daemon will simply refuse to work because it cannot use that filesystem for its cache. If the daemon doesn't run, you'll get a puzzling error message that might make you think you have a firewall problem. To get the daemon to work, edit the `/etc/openafs/afs.conf` to make it use the memory cache. It is said to be less stable than the hard disk cache. The {{{README.Debian}}} file also suggests creating a loopback ext2 filesystem for the cache. == Konqueror == |
== Konqueror Troubleshooting == |
| Line 92: | Line 34: |
''Is this still a problem? -- BtTempleton'' |
This is the chapter of the MemberManual that describes how to install and configure OpenAFS Client on Debian based systems. These instructions were adapted from HCoop user bpt's instructions.
These instructions have been tested on Debian wheezy.
OpenAFS Client Installation
To install the OpenAFS client and related programs, run apt-get install openafs-client openafs-krb5 krb5-user as root. Answer the configuration questions as follows:
AFS cell this workstation belongs to: hcoop.net
Default Kerberos version 5 realm: HCOOP.NET
You can accept the default values for other questions. If you're not prompted for these values, run dpkg-reconfigure -phigh openafs-client krb5-user.
Using AFS
To gain access to your HCoop AFS share, run kinit user@HCOOP.NET && aklog hcoop.net on your local system.
The tickets gained will last up to 10 hours but can be renewed with krenew for up to 8 days. Here's a common use:
krenew -K 30 -t
See the krenew man page to learn what these options are doing.
Konqueror Troubleshooting
Konqueror simply hangs when trying to browse /afs with the default CellServerDB. This happens because it is trying to access AFS volumes it doesn't have access to or that are not accessible, and hangs indefinitely. There is a lot of cells pre-configured in the Debian package, and probably some of them are not valid or not accessible. Once the content of /etc/openafs/CellServerDB has been erased of everything except for the hcoop.net entry, browsing /afs with Konqueror should work.
Is this still a problem? -- BtTempleton