> > If my application which is write()ing a large block of data > ever gets stuck > > in afs_osi_Sleep() then there is _absolutely_no_way_ that a > signal will ever > > get me out. I have to wait until something else interrupts > the sleep. How > > long do I have to wait? > > Perhaps it is a little strange, but AFS has always been a > real bear when > it gets stuck on a down server. Hitting ^C does no good at all; you > just have to wait for the client to decide the server is down.
This is probably the only major issue we have with AFS... In some cases, it seems like the client never gives up. How hard would it be to get the client daemon to be a little more impatient? i.e. more prone to switch servers in the case of replicated volumes? -- Nathan ------------------------------------------------------------ Nathan Neulinger EMail: [EMAIL PROTECTED] University of Missouri - Rolla Phone: (573) 341-4841 Computing Services Fax: (573) 341-4216 _______________________________________________ OpenAFS-devel mailing list [EMAIL PROTECTED] https://lists.openafs.org/mailman/listinfo/openafs-devel
