For AFS 3.3 there are "useful" features introduced, that I wish were
implemented differently (perhaps there's still time to put them in 3.3a or
3.4!)
1. The -notify flag for bos.
I wish this was called for all state changes of a Bos instance (and it
passed the new state as an argument!). Right now, it only reports an
instance going down!!! Anyway it's very easy to send a trap/alert when the
instance dies, but it's a real pain to send when it comes back on line.
Anyway, with this one simple change to -notify (reporting all state changes)
it would be more usable. BTW, we presently have a polling sub-agent
watching this as well. However, my experience is that the idea
combination for Distributed Systems Managements is a combination of
both polling and traps! (This let's you relax the polling intervals a
bit and thus reduce amount of bandwidth consumed by Management traffic!)
2. kpwvalid
I wish this exit was performed at the server end, not the client end.
Even though it has to be in the same directory as kpasswd, there's nothing
to stop a clever user from circumventing the whole thing by
copying kpasswd to the local file system and using a checker of his own
choosing.
I think it would be much more effective if the passwd was verified by
kasserver before it updated the kas db!
3. The monitors (afsmon, scout, etc)
I wish all of these had script exits when trigger conditions were met.
(Analogous to the -notify option in #1). My reasoning is the same as it
is for #1, as well.
