Matthew Jacob <[EMAIL PROTECTED]> writes: > Hmm. The client wasn't following symlinks. You sure? What happens is when you queue up an nfs operation provoked by following a symlink. I couldn't figure any other way of making that happen. > The patch seems simple enough, but it probably shouldn't just > swallow the error. Yeah, your patch to subr_prf.c is better. /assar To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
- is it possible to have a NULL procp for an NFS request? Matthew Jacob
- Re: is it possible to have a NULL procp for an NFS r... Assar Westerlund
- Re: is it possible to have a NULL procp for an N... Matthew Jacob
- Re: is it possible to have a NULL procp for ... Assar Westerlund
- Re: is it possible to have a NULL procp ... Matthew Jacob
- Re: is it possible to have a NULL procp ... Matt Dillon