From: "Steven Levine" <ecs-isp@2rosenthals.com>
Message-ID: <668616df.10.mr2ice.fgrirsq@earthlink.net>
Date: Wed, 03 Jul 2024 20:28:31 -0700
To: "eCS ISP Mailing List" <ecs-isp@2rosenthals.com>
In-Reply-To: <list-10146255@2rosenthals.com>
Subject: Re: [eCS-ISP] Bind 9.11.37 issue - ticket #784 - update

In <list-10146255@2rosenthals.com>, on 07/03/24
   at 07:17 PM, "Paul Smedley" <ecs-isp@2rosenthals.com> 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" <steve53@earthlink.net>  Warp/DIY/BlueLion etc.
www.scoug.com www.arcanoae.com www.warpcave.com
----------------------------------------------------------------------