Newsgroups: php.internals Path: news.php.net Xref: news.php.net php.internals:130375 X-Original-To: internals@lists.php.net Delivered-To: internals@lists.php.net Received: from php-smtp4.php.net (php-smtp4.php.net [45.112.84.5]) by lists.php.net (Postfix) with ESMTPS id 15AA81A00BC for ; Mon, 16 Mar 2026 20:26:34 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=php.net; s=mail; t=1773692798; bh=G9x9LB1wilpyBxSxSNEeCPTd9pLB7sxtS6vVHoEvQic=; h=Date:Subject:To:References:From:In-Reply-To:From; b=RcHif+Z/UKWm4E5Z3LvrdipoqnIOLAqqQJn46GjOQlDWklLUsbHRjnWdCg0gmFS3q twR+1M8/EKL1SVqNeNE1IDDUZ9jfHSIquUiTeFOCZZs7bw7m/oGBsL43VtC2nzpfsP SHpaY0Uu0TEbrgap84CqwNpMrWf/Z4XQrbQ1PDPaWvvZQm05I3hT+3JnCVXuDVhO1K WKxrOme9VjLgSMqu9+1md9oKVDiPXeGWn01VXylOWgu88GumkKTflhsa39m6YWF5ig znOu6A9Ti3FOjRgDJZAqxycxd9/FPUoZEyhlgXiEK8GxrEfAdy7M55mW89Jcifqv3z h8DzFityd9ZMQ== Received: from php-smtp4.php.net (localhost [127.0.0.1]) by php-smtp4.php.net (Postfix) with ESMTP id BEFC5180083 for ; Mon, 16 Mar 2026 20:26:34 +0000 (UTC) X-Spam-Checker-Version: SpamAssassin 4.0.1 (2024-03-25) on php-smtp4.php.net X-Spam-Level: X-Spam-Status: No, score=0.6 required=5.0 tests=BAYES_50,DKIM_SIGNED, DKIM_VALID,DKIM_VALID_AU,DKIM_VALID_EF,DMARC_PASS,SPF_HELO_NONE, SPF_PASS autolearn=no autolearn_force=no version=4.0.1 X-Spam-Virus: No X-Envelope-From: Received: from chrono.xqk7.com (chrono.xqk7.com [176.9.45.72]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (2048 bits) server-digest SHA256) (No client certificate requested) by php-smtp4.php.net (Postfix) with ESMTPS for ; Mon, 16 Mar 2026 20:26:34 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=bastelstu.be; s=mail20171119; t=1773692787; bh=vDAxvccySIRvFkqHcn4/8LYumrtubo+ec8JeiWDz93I=; h=Message-ID:Date:MIME-Version:Subject:To:References:From: In-Reply-To:Content-Type:from:to:cc:subject:message-id; b=MVrkT+eQARnmb2VwkZu7POd+TwrZEHmQ3JEO2Ggq1I+m5znCmK7CvRjtMDdZWRP9w iccyM+vRQIgaQc9G2JTwd5S1t0M9PUotPu9zm1sQ6YvMaQmLTiDp4q/7cd4yLYELcz G2HkzX/4K/OEjizdeByP/iTiGZ7GlLXmMXXi9BPJ+AvFXx5EN2cUxZVXhCIA+vqUiL EIiwk0YKKYp/xLL2HUotPhNDd1be6w5NKGyr+0wLdYnSi6Tz4j8rZ66br+Pe38y1eo ROAByTX5EdrGfB2bQ3bIlMiNa5YMsMMjfpOmnmuxKta93z1iZ6zPZYbzjW/mp+qn70 Xy2E/1A9/4H7A== Message-ID: <1c9534ff-d8c6-4939-a6f2-85a4c547ac0b@bastelstu.be> Date: Mon, 16 Mar 2026 21:26:26 +0100 Precedence: list list-help: list-unsubscribe: list-post: List-Id: x-ms-reactions: disallow MIME-Version: 1.0 Subject: Re: [PHP-DEV] [RFC] SNMP MIB reset function To: "swilton@fluentit.au" , internals@lists.php.net References: <5a2-69b78f00-11-50bc7700@253019388> Content-Language: en-US In-Reply-To: <5a2-69b78f00-11-50bc7700@253019388> Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 8bit From: tim@bastelstu.be (=?UTF-8?Q?Tim_D=C3=BCsterhus?=) Hi On 3/16/26 06:03, swilton@fluentit.au wrote: > I believe that the process is to send a message to the list, and gauge whether there is positive feedback before creating the RFC for voting.  Please let me know if I should create the RFC first? > The PR is here: https://github.com/php/php-src/pull/21452/changes I suspect that SNMP is such a specialized and rarely used extension that folks will be unable to meaningfully discuss an RFC for this feature - at least not without you doing quite a bit of explaining. This might be case where it's best to just find an informal agreement with you providing a well-tested and well-explained patch rather than doing a full RFC. ---------- That said, I did some research, finding this man page: https://linux.die.net/man/3/shutdown_mib. I'm seeing that the manpage states for init_mib(): > It should be called before any other routine that manipulates or accesses the MIB tree. I'm seing that init_mib() is not currently called at all in ext/snmp. Is the initialization implicitly happening as part of init_snmp()? For shutdown_mib() I'm seeing: > It is strongly recommended that one does not invoke shutdown_mib while there are SNMP sessions being actively managed. Will calling your proposed `snmp_init_mib()` function cause issues when an existing SNMP object is being used after the call to `snmp_init_mib()`? ---------- In your email you mention: > Another consideration is that the MIB tree persists across FPM requests because the MIB tree is kept as a global structure within SNMP library memory. Would calling `shutdown_mib()` in RSHUTDOWN (i.e. the end-of-request handler) solve the problem of the MIB persisting across requests or is it sometimes desirable that the MIB is persisted? Best regards Tim Düsterhus