Users at my site report odd symptoms when (as it turns out) they hit AFS quota limits. Most software doesn't check for this condition nor report anything near sensible. For example, one use reported elm as: > Hi Paul - I was using ELM on cachalot when it bombed out with the error: > Can't create lock file! Need write permission in "/usr/spool/mail/". Investigation revealed no problem with write permission but zero quota left. My questions: What do other AFS sites do to pre-empt user problems like this? Imagine the time that could be saved by making users aware they need to husband their available quota more carefully. Is it worth sweeping across all user volumes with something like "watcher" to check being close to quota exhaustion? Or have .profile (oops .login for you csh users) run a check at login? Please email me directly and I will post a summary. -- paul http://acm.org/~mpb/homepage.html FYI: "watcher" written by Kenneth Ingham, UNM Computing Center, Albuquerque, NM scans for exception conditions and notifys by whatever means you set up. See: ftp://src.doc.ic.ac.uk/usenet/comp.sources.unix/volume11/watcher/part01.gz ftp://src.doc.ic.ac.uk/usenet/comp.sources.unix/volume11/watcher/part02.gz
