On Tue, 20 May 2008, Krishna Srinivas wrote:
It is a bug in the way xlators notify UP/DOWN status to other xlators.
Ah, OK. I thought I was doing something wrong.
Thanks for notifying it to us :)
No problem, glad I could help. :) Is it likely to make it into release 1.3.10?
Workaround is having a separate process for "protocol/server" xlator.
Thanks. I split it all up back to client-side AFR. It works, but I think the way I was trying to use it would be more efficient for my setup.
Gordan
