In the short-term, we deal with blocking by taking over the network
send() and recv() functions, therefore making them 'semi-async'. This
-doens't apply to DNS yet.These thread-safety context-variables will
+doesn't apply to DNS yet.These thread-safety context-variables will
probably present porting problems, during the MIT port. This will
probably be most of the work in the port to MIT.
in libkrb5 would be difficult, but valuable.
* In the short-term, we deal with blocking by taking over the network
send() and recv() functions, therefore making them 'semi-async'. This
- doens't apply to DNS yet.These thread-safety context-variables will
+ doesn't apply to DNS yet.These thread-safety context-variables will
probably present porting problems, during the MIT port. This will
probably be most of the work in the port to MIT.
This may require more thorough thread-safe-ing work on the MIT libraries.
if (finfo2.basic_info.out.write_time != finfo3.basic_info.out.write_time) {
torture_result(tctx, TORTURE_FAIL,
- "qpathinfo time doens't match fileinfo time");
+ "qpathinfo time doesn't match fileinfo time");
ret = false;
}