1 openafs (1.5.77-1) experimental; urgency=low
3 This version of the OpenAFS file server includes a version built with
4 demand-attach, but as binaries with a different name.
6 Demand-attach completely changes how the file server shuts down and
7 starts up. Instead of detaching all volumes on shutdown and reattaching
8 them on startup, the file server saves state to disk and restores state
9 when starting, enabling it to start far faster. Volumes are only
10 attached when used and are detached again if they go unused for an
11 extended period. Volumes can also be salvaged on demand.
13 Demand-attach is recommended for new deployments and for evaluation in
14 current production deployments, but requires a change to your bos
15 configuration to use. If you want to switch your file server to
18 bos status localhost -instance fs -long
20 and take note of the flags that you're using with the fileserver and
23 bos stop localhost fs -localauth
24 bos delete localhost fs -localauth
25 bos create localhost dafs dafs \
26 "/usr/lib/openafs/dafileserver <fileserver-flags>" \
27 "/usr/lib/openafs/davolserver <volserver-flags>" \
28 /usr/lib/openafs/salvageserver /usr/lib/openafs/dasalvager
30 to create the correct new BosConfig entry for demand-attach AFS.
32 If you were running an earlier version of the experimental
33 openafs-filserver package, the way that demand-attach was handled has
34 changed and you have to change your bos configuration to use the new
35 demand-attach binary names. Run:
37 bos stop localhost dafs -localauth
38 bos delete localhost dafs -localauth
40 and then run the bos create command above. This only applies to users
41 of the previous experimental packages, not to upgrades from unstable.
43 -- Russ Allbery <rra@debian.org> Tue, 21 Sep 2010 14:08:04 -0700
45 openafs (1.5.73.3-1) experimental; urgency=low
47 As of this release, the default permissions for /etc/openafs/server are
48 now 0755, matching upstream. The only file in that directory that needs
49 to be kept secure is KeyFile, which is created with 0600 permissions.
50 The directory permissions won't be changed on upgrade, so bosserver will
51 complain now that it is no longer patched to permit restrictive
52 permissions. Once you're certain the per-file permissions of all files
53 in that directory are safe, chmod 755 /etc/openafs/server to make
56 -- Russ Allbery <rra@debian.org> Tue, 06 Apr 2010 14:51:52 -0700
58 openafs (1.4.4.dfsg1-4) unstable; urgency=low
60 The files previously located in /etc/openafs/server-local have been
61 moved to /var/lib/openafs/local. The OpenAFS fileserver and bosserver
62 write files to this directory on startup which are not configuration
63 files and therefore, per the File Hierarchy Standard, should not be in
64 /etc. Any sysid, sysid.old, NetInfo, and NetRestrict files in
65 /etc/openafs/server-local have been copied to /var/lib/openafs/local.
67 upserver and upclient have moved to /usr/lib/openafs (from /usr/sbin) to
68 match the other programs intended to be run by the bosserver and to
69 match upstream's layout. If you're running upserver or upclient from
70 bosserver, BosConfig has been updated with the new path, but the
71 services have not been restarted.
73 At your convenience, you should restart your servers with:
75 bos restart -all -bosserver
77 so that the running servers will look at the new locations. After doing
78 so, you may remove /etc/openafs/server-local if you wish.
80 -- Russ Allbery <rra@debian.org> Tue, 19 Jun 2007 03:51:58 -0700