Date: Sun, 11 Jul 1999 12:40:25 -0500 (CDT) From: toasty@dragondata.com To: FreeBSD-gnats-submit@freebsd.org Subject: ports/12596: pidentd is unstable in 3.2 and 4.0 Message-ID: <199907111740.MAA12537@celery.dragondata.com>
next in thread | raw e-mail | index | archive | help
>Number: 12596 >Category: ports >Synopsis: pidentd is unstable in 3.2 and 4.0 >Confidential: no >Severity: non-critical >Priority: low >Responsible: freebsd-ports >State: open >Quarter: >Keywords: >Date-Required: >Class: sw-bug >Submitter-Id: current-users >Arrival-Date: Sun Jul 11 10:50:00 PDT 1999 >Closed-Date: >Last-Modified: >Originator: Kevin Day >Release: FreeBSD 3.2-RELEASE i386 >Organization: DragonData Internet Services >Environment: Various 3.2 and 4.0 machines. >Description: pidentd seems to experience a lot of problems that I never saw on 2.2 systems. (I'm still running several 2.2 systems that pidentd is still happy in.) The most obvious problem is what's in my syslog: Jul 11 11:21:01 shell3 inetd[276]: /usr/local/sbin/identd[65111]: exit status 0x100 Jul 11 11:28:01 shell3 inetd[276]: /usr/local/sbin/identd[66194]: exit status 0x100 Jul 11 11:46:01 shell3 inetd[276]: /usr/local/sbin/identd[68698]: exit status 0x100 Jul 11 12:04:00 shell3 inetd[276]: /usr/local/sbin/identd[71084]: exit status 0x100 Jul 11 12:19:01 shell3 inetd[276]: /usr/local/sbin/identd[72912]: exit status 0x100 Jul 11 12:20:02 shell3 inetd[276]: /usr/local/sbin/identd[72968]: exit status 0x100 Jul 11 12:22:01 shell3 inetd[276]: /usr/local/sbin/identd[73371]: exit status 0x100 Jul 11 12:26:01 shell3 inetd[276]: /usr/local/sbin/identd[74013]: exit status 0x100 It seems to spit one of those out in about every 10-15 identd requests. Another problem is what I see from a ps: root 31786 0.0 0.1 840 272 ?? Is 23Jun99 0:00.02 identd -i 0 31786 276 7 2 0 840 272 sbwait Is ?? 0:00.02 identd -i root 22692 0.0 0.1 840 272 ?? Is Sun06PM 0:00.02 identd -i 0 22692 276 1 2 0 840 272 sbwait Is ?? 0:00.02 identd -i root 73632 0.0 0.1 840 272 ?? Is Tue03AM 0:00.02 identd -i 0 73632 276 4 2 0 840 272 sbwait Is ?? 0:00.02 identd -i root 48404 0.0 0.1 840 272 ?? Is Tue01PM 0:00.02 identd -i 0 48404 276 113 2 0 840 272 sbwait Is ?? 0:00.02 identd -i root 48405 0.0 0.1 840 272 ?? Is Tue01PM 0:00.02 identd -i 0 48405 276 113 2 0 840 272 sbwait Is ?? 0:00.02 identd -i root 44811 0.0 0.1 840 276 ?? Is Thu05PM 0:00.02 identd -i 0 44811 276 213 2 0 840 276 sbwait Is ?? 0:00.02 identd -i root 44891 0.0 0.1 840 276 ?? Is Thu05PM 0:00.02 identd -i 0 44891 276 173 2 0 840 276 sbwait Is ?? 0:00.02 identd -i root 45099 0.0 0.1 840 276 ?? Is Thu05PM 0:00.02 identd -i 0 45099 276 203 2 0 840 276 sbwait Is ?? 0:00.02 identd -i root 45100 0.0 0.1 840 276 ?? Is Thu05PM 0:00.02 identd -i 0 45100 276 180 2 0 840 276 sbwait Is ?? 0:00.02 identd -i root 45101 0.0 0.1 840 276 ?? Is Thu05PM 0:00.02 identd -i 0 45101 276 180 2 0 840 276 sbwait Is ?? 0:00.02 identd -i root 49238 0.0 0.1 840 276 ?? Is Thu05PM 0:00.02 identd -i 0 49238 276 176 2 0 840 276 sbwait Is ?? 0:00.02 identd -i root 78976 0.0 0.1 840 360 ?? Is 12:49AM 0:00.02 identd -i 0 78976 276 31 2 0 840 360 sbwait Is ?? 0:00.02 identd -i I end up getting lots of stuck identd processes. They're easily killable, but tend to build up fast. The third problem I see is that identd will run, but return 'NO-USER' to all requests, until I kill it and let inetd spawn another. >How-To-Repeat: I'm running servers with 300-500 processes each connecting to servers that will make identd requests when they first start up. My password file has about 1000 lines in it. It shouldn't be too hard to reproduce these. >Fix: Unknown, I haven't really tried debugging this. >Release-Note: >Audit-Trail: >Unformatted: To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-ports" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?199907111740.MAA12537>