On Thu, Jan 22, 2009 at 10:59:49AM -0500, Steve Dickson wrote: > J. Bruce Fields wrote: > > > > On the mount case specifically: How far are we from the idea of a mount > > program that can identify most problems itself? I know its error > > reporting has gotten better.... > > > > I suppose the main feedback mount gets right now is an error code from > > the mount system call, and that may be too narrow an interface to cover > > most problems. Is there some way we can give mount a real interface it > > can use to find out this stuff instead of just dumping more strings into > > the logs? > Interesting.... Store something like a reason code (similar to what they have > in he Kerberos) Maybe. > in somewhere in the proc file system? But then I don't know how you'd associate it with a particular mount attempt. --b. > Its seems to me this is a common problem among network file systems... -- To unsubscribe from this list: send the line "unsubscribe linux-nfs" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
