I believe I am witnessing this bug with a particular connecting host. I'm running lenny on i386, and it seems there is an additional symptom that appears when this bug bites besides what has been described so far.
a spawn command in hosts.allow never executes for this particular host. it's not that the file /home/root/data/getfuzzy.host is left empty, but that it never is created at all. for any other host connecting to that service, the file is created and will contain the host name or address. [inetd.conf] wserv2 stream tcp nowait root /usr/sbin/tcpd /home/root/bin/in.getfuzzy -h -L /home/root/bin/getfuzzy.sh [hosts.allow] in.getfuzzy: ALL:spawn echo %h > /home/root/data/getfuzzy.host [syslog] Feb 11 10:01:16 linear in.getfuzzy[2406]: connect from 99.29.154.194 (99.29.154.194) Feb 11 10:01:51 linear in.getfuzzy[2409]: connect from 99.29.154.194 (99.29.154.194) Feb 11 10:02:19 linear in.getfuzzy[2464]: connect from 99.29.154.194 (99.29.154.194) Feb 11 10:03:03 linear in.getfuzzy[2480]: connect from 99.29.154.194 (99.29.154.194) Feb 11 10:03:44 linear in.getfuzzy[2497]: connect from 99.29.154.194 (99.29.154.194) robh@linear:~$ host 99.29.154.194 194.154.29.99.in-addr.arpa domain name pointer 99-29-154-194.lightspeed.bcvloh.sbcglobal.net. robh@linear:~$ host 99-29-154-194.lightspeed.bcvloh.sbcglobal.net 99-29-154-194.lightspeed.bcvloh.sbcglobal.net has address 99.29.154.194 robh@linear:~$ -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
