packages. If you are not already familiar with the basic concepts of
OpenAFS, you should review the documentation at:
- <http://www.openafs.org/doc/index.htm>
+ http://docs.openafs.org/
particularly the AFS Administrator's Guide. This documentation is
somewhat out of date (it doesn't talk about how to use a Kerberos v5 KDC
3. If the machine is to be a file server, create an fs instance using
bos create:
- bos create <host> fs fs -cmd /usr/lib/openafs/fileserver \
- -cmd /usr/lib/openafs/volserver \
+ bos create <host> fs fs -cmd /usr/lib/openafs/dafileserver \
+ -cmd /usr/lib/openafs/davolserver \
+ -cmd /usr/lib/openafs/salvageserver \
-cmd /usr/lib/openafs/salvager -localauth
For a file server, this is all you have to do. The above uses the
-b 240 -vc 1200
If you want to add any additional fileserver options, enclose
- /usr/lib/openafs/fileserver and the following options in double
+ /usr/lib/openafs/dafileserver and the following options in double
quotes when giving the bos create command.
+ This creates a demand-attach fileserver, which is recommended for
+ new installations. You can also create a regular fileserver if you
+ prefer. See the bos_create(8) man page for more information.
+
4. For database servers, also install openafs-dbserver and then use bos
addhost to add the new server to /etc/openafs/server/CellServDB:
# Create a file server as well.
run("bos create $server dafs dafs"
- . " -cmd '/usr/lib/openafs/fileserver $fs_options'"
- . " -cmd /usr/lib/openafs/volserver"
+ . " -cmd '/usr/lib/openafs/dafileserver $fs_options'"
+ . " -cmd /usr/lib/openafs/davolserver"
. " -cmd /usr/lib/openafs/salvageserver"
- . " -cmd /usr/lib/openafs/salvager");
+ . " -cmd /usr/lib/openafs/dasalvager");
unwind("bos delete $server fs -localauth");
# Make sure that there is no scheduled general restart time; it's not needed.
- Fix potential kernel panic during bulkstatus.
- Better vos dry-run mode for syncvldb and syncserv.
- Fix s390x kernel build support.
+ * Update afs-newcell and README.servers to recommend using the
+ demand-attach fileserver binaries and dafs bos type.
* The openafs-fileserver init script now depends on $named since
apparently the volserver requires DNS during startup. Thanks, Jaap
Winius. (Closes: #589783)
-openafs (1.5.73.3-1) experimental; urgency=low
+openafs (1.5.77-1) experimental; urgency=low
+
+ This version of the OpenAFS file server includes a version built with
+ demand-attach, but as binaries with a different name.
- This version of the OpenAFS file server is built with demand-attach.
Demand-attach completely changes how the file server shuts down and
starts up. Instead of detaching all volumes on shutdown and reattaching
them on startup, the file server saves state to disk and restores state
attached when used and are detached again if they go unused for an
extended period. Volumes can also be salvaged on demand.
- Demand-attach is experimental. Please only use this file server for
- testing. It is not yet ready to run in a production environment.
-
- This change REQUIRES changes to your BosConfig file so that the file
- server will start properly. After installing the new openafs-fileserver
- package, run:
+ Demand-attach is recommended for new deployments and for evaluation in
+ current production deployments, but requires a change to your bos
+ configuration to use. If you want to switch your file server to
+ demand-attach, run:
bos status localhost -instance fs -long
bos stop localhost fs -localauth
bos delete localhost fs -localauth
bos create localhost dafs dafs \
- "/usr/lib/openafs/fileserver <fileserver-flags>" \
- "/usr/lib/openafs/volserver <volserver-flags>" \
- /usr/lib/openafs/salvageserver /usr/lib/openafs/salvager
+ "/usr/lib/openafs/dafileserver <fileserver-flags>" \
+ "/usr/lib/openafs/davolserver <volserver-flags>" \
+ /usr/lib/openafs/salvageserver /usr/lib/openafs/dasalvager
to create the correct new BosConfig entry for demand-attach AFS.
+ If you were running an earlier version of the experimental
+ openafs-filserver package, the way that demand-attach was handled has
+ changed and you have to change your bos configuration to use the new
+ demand-attach binary names. Run:
+
+ bos stop localhost dafs -localauth
+ bos delete localhost dafs -localauth
+
+ and then run the bos create command above. This only applies to users
+ of the previous experimental packages, not to upgrades from unstable.
+
+ -- Russ Allbery <rra@debian.org> Tue, 21 Sep 2010 14:08:04 -0700
+
+openafs (1.5.73.3-1) experimental; urgency=low
+
As of this release, the default permissions for /etc/openafs/server are
now 0755, matching upstream. The only file in that directory that needs
to be kept secure is KeyFile, which is created with 0600 permissions.
debian/tmp/usr/sbin/voldump usr/sbin
debian/tmp/usr/sbin/volinfo usr/sbin
+debian/tmp/usr/lib/openafs/dafileserver usr/lib/openafs
+debian/tmp/usr/lib/openafs/dasalvager usr/lib/openafs
+debian/tmp/usr/lib/openafs/davolserver usr/lib/openafs
debian/tmp/usr/lib/openafs/fileserver usr/lib/openafs
debian/tmp/usr/lib/openafs/salvager usr/lib/openafs
debian/tmp/usr/lib/openafs/salvageserver usr/lib/openafs
debian/tmp/usr/share/man/man8/bos_util.8 usr/share/man/man8
debian/tmp/usr/share/man/man8/bosserver.8 usr/share/man/man8
+debian/tmp/usr/share/man/man8/dafileserver.8 usr/share/man/man8
+debian/tmp/usr/share/man/man8/dasalvager.8 usr/share/man/man8
+debian/tmp/usr/share/man/man8/davolserver.8 usr/share/man/man8
debian/tmp/usr/share/man/man8/fileserver.8 usr/share/man/man8
debian/tmp/usr/share/man/man8/fssync-debug.8 usr/share/man/man8
debian/tmp/usr/share/man/man8/fssync-debug_attach.8 usr/share/man/man8
projects / packages / o / openafs.git / commitdiff