Package: innduct Version: 2.1~~iwj3 Severity: important Tags: upstream I have had trouble over the past few days with innduct generating unreasonable amounts of debug log. Mostly, the messages look like this:
Oct 18 08:40:01 chiark innduct[3270]: nntp.[elided]| debug: filemon inotify: read event with unknown wd=5447913 Oct 18 08:40:01 chiark innduct[3270]: nntp.[elided]| debug: filemon inotify: startfile 0x55de6bf4e6b0 wd=5447914 pf=0x55de6c096840 Oct 18 08:40:01 chiark innduct[3270]: nntp.[elided]| debug: filemon inotify: stopfile 0x55de6bf4e6b0 wd=5447914 pf=0x55de6c096840 Oct 18 08:40:01 chiark innduct[3270]: nntp.[elided]| debug: filemon inotify: read event with unknown wd=5447914 Oct 18 08:40:01 chiark innduct[3270]: nntp.[elided]| debug: filemon inotify: startfile 0x55de6bf4e6b0 wd=5447915 pf=0x55de6bfbfd10 Oct 18 08:40:01 chiark innduct[3270]: nntp.[elided]| debug: filemon inotify: stopfile 0x55de6bf4e6b0 wd=5447915 pf=0x55de6bfbfd10 Oct 18 08:40:01 chiark innduct[3270]: nntp.[elided]| debug: filemon inotify: startfile 0x55de6bf4e6b0 wd=5447916 pf=0x55de6bff38d0 This seems to have been triggered by the peer being in "expiring" state for several days and responding to every article with 431. I think I have diagnosed the problem. If my fix holds up, I will upload it. -- System Information: Debian Release: 11.11 APT prefers oldstable-security APT policy: (500, 'oldstable-security'), (500, 'oldstable') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 5.10.0-28-amd64 (SMP w/16 CPU threads) Locale: LANG=C.UTF-8, LC_CTYPE=C.UTF-8 (charmap=UTF-8), LANGUAGE not set Shell: /bin/sh linked to /bin/dash Init: sysvinit (via /sbin/init) LSM: AppArmor: enabled Versions of packages innduct depends on: ii libc6 2.31-13+deb11u11 ii liboop4 1.0.1-2.1 Versions of packages innduct recommends: ii perl 5.32.1-4+deb11u3 innduct suggests no packages. -- no debconf information
