On Tue, 16 Aug 2005, Russ Allbery wrote:
I was hoping that the default logic in afsd could be updated to
something useful (hence my patch), and that we then could remove the
various tuning made in the init scripts due to the fact that afsd
didn't do reasonable tuning by default.
Oh, I'm sure it will! That's just likely not a 1.4.0 thing, so I went
ahead and did something similar directly in the init script for the Debian
unstable packages so that we can get some early experience with it. I'm
hoping to thereby get some evidence to back up including this change into
1.4.1 or 1.4.2.
Changes like this should be done in the development series, which is
1.3.x. When you get to stable, you don't want to surprise users by
changing behaviour.
Someone really ought to update the afsd manpage, the options available
and the options documented differ quite a lot.
There are no man pages; there are text documents that are formatted
vaguely like man pages but aren't really useful substitutes. I have a
patch to start the process of converting the HTML documents to POD so that
we have man pages that we can really update. This too is something for
after 1.4.0.
I beg to differ. Proper documentation is a must in a stable release,
I'd even say it's a release criteria. Todays situation of having a
plethora of undocumented tuning options is most likely to annoy many
users (including me).
/Nikke
--
-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-
Niklas Edmundsson, Admin @ {acc,hpc2n}.umu.se | [EMAIL PROTECTED]
---------------------------------------------------------------------------
* <- Tribble # <- Electrocuted tribble.
=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=
_______________________________________________
OpenAFS-devel mailing list
[email protected]
https://lists.openafs.org/mailman/listinfo/openafs-devel
