From owner-freebsd-hackers Tue Aug 7 8: 8: 7 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from southpass.baynetworks.com (ns2.BayNetworks.COM [134.177.3.16]) by hub.freebsd.org (Postfix) with ESMTP id 1ACEA37B409 for ; Tue, 7 Aug 2001 08:08:04 -0700 (PDT) (envelope-from bwithrow@BayNetworks.COM) Received: from mailhost.BayNetworks.COM (ns1.baynetworks.com [134.177.1.107]) by southpass.baynetworks.com (8.9.1/8.9.1) with ESMTP id HAA24167 for ; Tue, 7 Aug 2001 07:57:03 -0700 (PDT) Received: from pobox.engeast.BayNetworks.COM (pobox.engeast.baynetworks.com [192.32.61.6]) by mailhost.BayNetworks.COM (8.9.1/8.8.8) with ESMTP id IAA01506 for ; Tue, 7 Aug 2001 08:05:38 -0700 (PDT) Received: from baynetworks.com (tuva [192.32.150.102]) by pobox.engeast.BayNetworks.COM (SMI-8.6/BNET-97/04/24-S) with ESMTP id LAA18256; Tue, 7 Aug 2001 11:07:47 -0400 for Message-Id: <200108071507.LAA18256@pobox.engeast.BayNetworks.COM> X-Mailer: exmh version 2.3.1 01/18/2001 with nmh-1.0.4 To: hackers@freebsd.org Cc: bwithrow@engeast.BayNetworks.COM Subject: Ypbind malfunction on 4.x Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Tue, 07 Aug 2001 11:07:48 -0400 From: Robert Withrow Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG Hi: If I'm posting to the wrong list, please let me know. There is a long-running problem in FreeBSD's yp/ypbind that is evidenced by: Aug 4 02:01:43 tuva ypbind[160]: NIS server [192.32.150.15] for domain "engeast" not responding Aug 4 02:02:14 tuva last message repeated 30 times Aug 4 02:04:15 tuva last message repeated 121 times (And there would be other messages about throttling icmp messages, except I've applied a patch to ypbind.c that at least throttles things down to 1 message per second. This patch was posted to questions.) ... and it never rebinds to any other server. The only way I've found to fix the problem is to reboot. I am experiencing this in 4.3 Release, and I've had it in 4.2 and earlier. This problem has seen a little discussion in questions. But I've never seen anything in any of the lists about a solution to the core problem. Maybe I've missed this? Anyone working on this? It is a pretty serious problem (since you basically can't do anything once it happens in typical NIS/Amd installations). I'd appreciate, at least, knowing if there is a non-reboot work-around. Thanks! -- Robert Withrow -- (+1 978 288 8256, ESN 248) BWithrow@NortelNetworks.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message