> If neither of those work, then maybe we should adapt ktrace to > support many simultaneous ktraces of a single process, but I don't > want to commit more resources to maintaining that unless we have a > real need.
Well, it seems to me that the choices are: (1) Keep meta-make as it is, filemon and all; (2) Switch meta-make to ktrace and ignore the debuggability lose; (3) Switch meta-make to ktrace and support multi-ktrace; (4) Drop meta-make. When I started this conversation I was not aware of what dholland just said, that meta-make is apparently a single-person thing that somehow wound up in the main tree anyway. This makes me now think that perhaps (4) is the best option for NetBSD's main tree, next best being (2) in the practical immediate term or (3) if we want to be idealistic. Since it appears sjg is happy with (2), the only thing I now think needs to be done (and even this is pretty mild) is warnings in the documentation for make's meta mode[%] noting that it uses ktrace and thus is incompatible with other uses of ktrace on the relevant processes. [%] If there is any - man.netbsd.org has been improved to the point where it won't talk to me. /~\ The ASCII Mouse \ / Ribbon Campaign X Against HTML mo...@rodents-montreal.org / \ Email! 7D C8 61 52 5D E7 2D 39 4E F1 31 3E E8 B3 27 4B