Hmm. I've just put an AFS client on one of our "general purpose" Unix hosts. This machine, which has a lot of local disk, is taken down to single-user once a week so that a full dump can be done on the quiescent file system. afsd isn't too fond of this - it gets upset when /usr is umounted. The key here is that the "gp" client machine *isn't* rebooted - just brought down to single-user, dumped, and kicked to multi-user again. This is the first machine I've put an AFS client on that does this - on other machines, if I want to kill afsd I "shutdown -r" and don't run rc.afs at the reboot. I'm not really sure if that's an option for this machine or not - the machine isn't under my direct control. Transarc didn't have a better idea (afsd may or may not have been modified to be kill-able, but it's certainly not yet to the point where it can be restarted, once stopped) - does anyone out there do this and have a work-around? If it makes any difference, this is a pmax_ul43 AFS 3.2b client. Thanks. Pat Wilson Manager, Academic Unix Systems Group Dartmouth College [EMAIL PROTECTED]
