> In 2.4 it is entirely possible to have a record broken up into two > reads. There is no guarantee that the two reads will be reading the > same record. Let me make sure I understand what you're saying here... You're saying that since pidentd is calling fgets(), that can actually result in multiple read() calls. Because of this, the first half of the line containing the address:port pairs can be with respect to one socket, and the second half containing the euid can be from another socket? Chad - : send the line "unsubscribe linux-net" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html