From: "Steven Levine" Received: from [192.168.100.201] (HELO mail.2rosenthals.com) by 2rosenthals.com (CommuniGate Pro SMTP 5.4.10) with ESMTP id 10148424 for ecs-isp@2rosenthals.com; Thu, 04 Jul 2024 00:11:41 -0400 Received: from [192.168.200.201] (port=58082 helo=mail2.2rosenthals.com) by mail.2rosenthals.com with esmtp (Exim 4.97.1) (envelope-from ) id 1sPDoW-000000006H1-19U4 for ecs-isp@2rosenthals.com; Thu, 04 Jul 2024 00:11:20 -0400 Received: from mta-202a.earthlink-vadesecure.net ([51.81.232.240]:56785) by mail2.2rosenthals.com with esmtps (TLS1.2) tls TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256 (Exim 4.97.1) (envelope-from ) id 1sPDoR-0000000062W-0BmH for ecs-isp@2rosenthals.com; Thu, 04 Jul 2024 00:11:15 -0400 DKIM-Signature: v=1; a=rsa-sha256; bh=9qgBeFkGj9odHDb6DDODgvE0J2bMDLUdSBe4Oj hfvWM=; c=relaxed/relaxed; d=earthlink.net; h=from:reply-to:subject: date:to:cc:resent-date:resent-from:resent-to:resent-cc:in-reply-to: references:list-id:list-help:list-unsubscribe:list-subscribe:list-post: list-owner:list-archive; q=dns/txt; s=dk12062016; t=1720066273; x=1720671073; b=Q7dEUCbRKcp3UDb8vvZQlNc8cQXXCcPyGBL+vU8HwphyU5A9VR8PUuE rq5oYjqvY+4K55AagcoR0YZJJUxUZRPTJJIq5Msa3Mg3q0Vyp3zfDM4NLHxKuJcVThDAekw Jsjg7y9fOl7k9HD2pvFWGIPBHVHcVMEeS8yE+bEg6W9SyMjj/DjlwMtLuq1neDeiPSghjPS R+WkfrxSLqDFLevwiiLnuPdp6FqJhqqVY+DrCz6oWMd9lYi3pE9aCbJgXKq5TYO7RFTp2mB XcMW0l7DEjXys5Z6tOD95FelnpF5eZw0EWJhQCDeFRKigTBNCQf/kZbLLBpSY6xhZyoIyj/ 0aA== Received: from slamain ([172.56.189.10]) by vsel2nmtao02p.internal.vadesecure.com with ngmta id 4246d662-17dee72989850aef; Thu, 04 Jul 2024 04:11:13 +0000 Message-ID: <668616df.10.mr2ice.fgrirsq@earthlink.net> Date: Wed, 03 Jul 2024 20:28:31 -0700 To: "eCS ISP Mailing List" In-Reply-To: Subject: Re: [eCS-ISP] Bind 9.11.37 issue - ticket #784 - update X-Mailer: MR/2 Internet Cruiser Edition for OS/2 v3.00.11.24/60 In , on 07/03/24 at 07:17 PM, "Paul Smedley" said: Hi Paul, As I suspected the 100% issue is on some other thread - specifically thread 2. You might recall that a build a monitorthreads utility back when and it showed the looping thread immediately. The looping code seems to include lib\isc\unix\socket.c:1418 while (cmsgp != NULL) { socket_log(sock, NULL, TRACE, isc_msgcat, ISC_MSGSET_SOCKET, ISC_MSG_PROCESSCMSG, "processing cmsg %p", cmsgp); and the message queue never empties. Assuming that there really are messages to be logged, I need to figure out how to turn on the logging for is class of messages. Under the debugger this code: lib\isc\unix\socket.c:1423 #ifdef ISC_PLATFORM_HAVEIN6PKTINFO if (cmsgp->cmsg_level == IPPROTO_IPV6 && cmsgp->cmsg_type == IPV6_PKTINFO) { seems to be enabled. Should ISC_PLATFORM_HAVEIN6PKTINFO really be defined? Thanks, Steven -- ---------------------------------------------------------------------- "Steven Levine" Warp/DIY/BlueLion etc. www.scoug.com www.arcanoae.com www.warpcave.com ----------------------------------------------------------------------