| 1 | This file explains how to operate a Zephyr service once you have |
|---|
| 2 | installed Zephyr on all the relevant machines and file servers in your |
|---|
| 3 | environment. To learn how to configure, build, and install Zephyr, |
|---|
| 4 | read the file INSTALL. |
|---|
| 5 | |
|---|
| 6 | To set up Zephyr service at a site, follow these steps: |
|---|
| 7 | |
|---|
| 8 | 1. Choose the machines you wish to have act as Zephyr servers at your |
|---|
| 9 | site. Expect the server to be CPU-efficient but to consume a bit more |
|---|
| 10 | memory than you might expect (at MIT, with around a thousand |
|---|
| 11 | simultaneous users, the Zephyr server's data size is 40MB). If you |
|---|
| 12 | have a lot of users, the server should have enough memory so that the |
|---|
| 13 | process doesn't swap. |
|---|
| 14 | |
|---|
| 15 | 2a. If you configured Zephyr with Hesiod support, make sure your |
|---|
| 16 | Hesiod realm has a "zephyr.sloc" entry containing a record for each |
|---|
| 17 | server. (Each entry should contain the name of the server, nothing |
|---|
| 18 | else.) The Zephyr servers will use the zephyr.sloc entry to find the |
|---|
| 19 | other servers. Host managers will use the zephyr.sloc entry to find |
|---|
| 20 | the Zephyr servers by default; however, you can control the set of |
|---|
| 21 | servers for each host manager by giving each host a |
|---|
| 22 | "<hostname>.cluster" entry containing a record "zcluster <serverset>". |
|---|
| 23 | If such a record is found, the host manager will resolve |
|---|
| 24 | "<serverset>.sloc" instead of "zephyr.sloc". |
|---|
| 25 | |
|---|
| 26 | 2b. If you configured Zephyr without Hesiod support, and you have |
|---|
| 27 | multiple Zephyr servers, each server should have a file "server.list" |
|---|
| 28 | in the configuration directory (which is /etc/athena/zephyr if you |
|---|
| 29 | configured with --enable-athena, or /usr/local/etc/zephyr if you |
|---|
| 30 | installed Zephyr in /usr/local and didn't use --enable-athena). This |
|---|
| 31 | file should contain a list of the servers, one per line. |
|---|
| 32 | |
|---|
| 33 | 3. If you configured Zephyr with Kerberos 4 support, make a service |
|---|
| 34 | key "zephyr.zephyr@<your realm>" and install a srvtab for that service |
|---|
| 35 | as "srvtab" in the configuration directory of each of your zephyr |
|---|
| 36 | servers. |
|---|
| 37 | |
|---|
| 38 | 4. Start zephyrd from the system binary directory (/usr/athena/etc if |
|---|
| 39 | you configured with --enable-athena, /usr/local/sbin if you installed |
|---|
| 40 | in /usr/local and didn't use --enable-athena). zephyrd logs as |
|---|
| 41 | service "local6"; watch the syslogs for error messages. Arrange for |
|---|
| 42 | zephyrd to be run at boot time on your server machines. |
|---|
| 43 | |
|---|
| 44 | 5. Each client machine should run zhm (the Zephyr Host Manager) from |
|---|
| 45 | the local system binary directory (/etc/athena for --enable-athena, |
|---|
| 46 | /usr/local/sbin if you installed in /usr/local and didn't use |
|---|
| 47 | --enable-athena). If you built Zephyr without Hesiod support, you |
|---|
| 48 | should start zhm as "zhm server1 server2 server3 ..." so that zhm |
|---|
| 49 | knows where the Zephyr servers are. Do not use "localhost" or |
|---|
| 50 | "127.0.0.1" as a server name, or zhm will become confused. |
|---|
| 51 | |
|---|
| 52 | You can send a SIGFPE signal to the server process to make it dump its |
|---|
| 53 | subscription database to /var/tmp/zephyr.db. (If /var/tmp didn't |
|---|
| 54 | exist when Zephyr was built, the subscription database will be dumped |
|---|
| 55 | in /usr/tmp or /tmp instead.) |
|---|
