Hi, On Thu, Jun 26, 2008 at 07:31:12PM +0200, zhengda wrote: > [EMAIL PROTECTED] wrote:
>> If we want to override the TCP/IP stack, that doesn't mean we want to >> override the pipe server as well, or the other way round... >> > I think using the symbolic link to the default server is another a > solution. Yes, it would work. But it would be an ugly solution: Only handling a rather unusual case directly, and the much more important case only through a kludge... Note that if you expand on that idea, you could just as well construct a whole filesystem with symlinks and/or unionfs, and chroot into it... No need for special server overriding mechanisms at all, if you want to go down that route ;-) (Note that some of the variants I suggested for server overriding mechanisms are technically actually not that far from that, only putting it in a more elegant and convenient framework... But that's a different story :-) ) >>> server = __file_name_lookup (np, 0, 0); >>> if (domain <= max_domain) >>> - servers[domain] = server; >>> + servers[domain] = server; >>> + if (name) >>> + free(name); >>> > Do you mean the indentation here? It is caused by '-' and '+' in the > beginning of lines. Ah, I see it now. That shouldn't happen, though. How did you generate the patch? -antrik-
