To my knowledge, it is not possible (ie has not been implimented) to
determine who has valid tokens or what client machines are currently
holding valid tokens. Although it would be possible to impliment a
system to track tokens (when issued, to whom, for what lifetime, to
which client) on the DBserver machines as they are allocated by the
kaserver, at quick glance, it seems difficult to guarantee that those
tokens are still valid once delivered to the client. Token expiration
isn't the problem. How can tokens that have been unlogged,
overwritten by new tokens, or just rebooted away be tracked?
That being said - although the people who's home volume resides on the
server to be shut down will *definately* be effected by the shutdown,
it is unwise to assume that other users would *not* be effected. All
unreplicated volumes, user home volumes or otherwise, will be
unavailable once the machine is shutdown. So if you have volumes
allocated for projects, departments, company-wide info, bboards,
license directories for software packages, etc etc - unavailability of
these volumes may cause problems for a difficult-to-determine set of
users.
Practice at most sites has been to notify *all* users of unscheduled
shutdowns - either via a P.A. system (Transarc's solution) or via
console messages to all AFS clients (CMU's solution - and probably
many others).
Pierette VanRyzin
