From owner-freebsd-hackers Mon Jan 25 08:33:56 1999 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id IAA06408 for freebsd-hackers-outgoing; Mon, 25 Jan 1999 08:33:56 -0800 (PST) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from excalibur.oceanis.net (ns.dotcom.fr [194.133.21.11]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id IAA06399 for ; Mon, 25 Jan 1999 08:33:54 -0800 (PST) (envelope-from pixel@excalibur.oceanis.net) Received: (from pixel@localhost) by excalibur.oceanis.net (8.9.1/8.9.1) id QAA11654 for freebsd-hackers@FreeBSD.ORG; Mon, 25 Jan 1999 16:33:51 GMT From: Emmanuel DELOGET Message-Id: <199901251633.QAA11654@excalibur.oceanis.net> Subject: SNMP devlmp with sysctl To: freebsd-hackers@FreeBSD.ORG Date: Mon, 25 Jan 1999 17:33:51 +0100 (MET) MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I'm sorry to disturb you. This mail was post to freebsd-net (this may be an error, since I did not get any response... but nobody may be instersted). I want to know if a kernel-level SNMP is planned . Notice that I've allready read the discussions about sysctl and SNMP in the mail archives. The things I thought about was not related to this stuff (well, not really related to...). Since SNMP is generally used in statis network elements (nasty things that does not require to be rebuild each day), it may be a good idea to replace the current sysctl tree by a new, SNMP-compliant one. This may need a more evolutive way to specify new sysctl entries (a kind of source code generator could be helpful). I'm currenlty working on this stuff, but I want to know if someone has allready do the same. -- pixel@dotcom.fr ------------------------------------------ DotCom Communication Numerique -- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message