[OpenAFS] Initial configuring openafs server: got some obscured errors

[Jeffrey Altman]

This is an OpenPGP/MIME signed message (RFC 2440 and 3156)
--------------enig261A28339F1F031CB3BFD3D8
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: quoted-printable

On 5/28/2012 9:46 AM, ayvango wrote:
>=20
> ---- On Fri, 25 May 2012 05:15:17 -0700 Derrick Brashear  wrote ----=20
>=20
>> On Fri, May 25, 2012 at 7:29 AM, ayvango  wrote:=20
>=20
>>> The documentation on the official site seemed to be outdated,=20
>>
>> It's still correct.=20
>=20

Can you be more specific regarding which documentation you are referring
to?  http://docs.openafs.org/ provides:

 * Reference Manual
   http://docs.openafs.org/Reference/index

 * UNIX Quick Start Guide
   http://docs.openafs.org/QuickStartUnix/index.html

 * Administration Guide
   http://docs.openafs.org/AdminGuide/index.html

 * User Guide
   http://docs.openafs.org/UserGuide/index.html

> It recommends to use klog instead of aklog that is considered obsolete.=
=20

Can you point out which of the above guides is out of date?  Or are you
referring to something else?

> What degree I can rely on this document to?
> It states average uptime is 2 weeks due to memory leakage.

It used to be that AFS servers were configured to automatically restart
each Sunday.  This is no longer required.   The uptime of many publicly
available servers is more than a year.   Memory leaks should be a thing
of the past.  Where is this reference?

> Is it still persist on modern AFS realizations?
> Do they retain 22 symbols on volumes 8 symbols on usernames limitations=
?

Volume names are still short.

Where did you find a reference to user names being 8 octets?

> Do unicode characters count as two?

UNICODE when stored in a filesystem is encoded using UTF-8.  The number
of octets required to store a UNICODE character as UTF-8 varies from one
to four depending on the numeric value associated with the character.

Jeffrey Altman





--------------enig261A28339F1F031CB3BFD3D8
Content-Type: application/pgp-signature; name="signature.asc"
Content-Description: OpenPGP digital signature
Content-Disposition: attachment; filename="signature.asc"

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.9 (MingW32)

iQEcBAEBAgAGBQJPw4rBAAoJENxm1CNJffh4HN8H/0IvhoUHEsvtSJjjn3B2dAGY
hI5H7X+MXtwtOXKk+exJhY2cblmedUbH+WEa00sadzRTz0z4K6Y2lwR75rqqidu8
vxCFh1mDFOmyVv56XScE+4krYyRhkrttuSAOQFhMLt/MI5JMOjqy8Gzobve/K7aE
SJGjhbnHzB2e/LYKKsS5tkdGYThDFrMbn/cCMt0ZbUHXfVb2g2kBUvTilpGNT4tj
8bbiHTQm0kQzuR4RarkjbUE2X4A2k5/peMvgSm4//aQ2NhKotfsE3W+PeFFbD3cz
YJxQKtMdArFpafE8RwjnZ5YK5WN3rDjHtreJeIMv7OJnU/KHFqpn5woJc/aijaU=
=BlyV
-----END PGP SIGNATURE-----

--------------enig261A28339F1F031CB3BFD3D8--