> If we cared more about compat with past openbsd releases, then it > would be -q 0, but if I'm not mistaken, we're leaning towards switching > behavior to be compatible with gnu netcat by default.
Actually, OpenBSD nc is the incompatible one. hobbit nc did not do shutdown. gnu nc does not do shutdown. FreeBSD is considering not doing nc, either, or at least that is what their "-q" flag was for. Debian people are upset about it too, and if we change this to no shutdown() by default, we'll do everyone a favor. Look at it this way. Truncated output from some query is the worst case -- it is a mysterious "sometimes you get scewed" behaviour. By default, I want to get the maximum. If I encounter a service that hangs at end of output, I can use the -N flag, and then I am satisfied. One of these situation has spurious data loss; the other has a visible "hang" that you can see happening, and then resolve using a flag.
