From owner-freebsd-questions  Sun Sep 22 11:54:33 1996
Return-Path: owner-questions
Received: (from root@localhost)
          by freefall.freebsd.org (8.7.5/8.7.3) id LAA00698
          for questions-outgoing; Sun, 22 Sep 1996 11:54:33 -0700 (PDT)
Received: from lariat.lariat.org ([129.72.251.2])
          by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id LAA00650
          for <freebsd-questions@freebsd.org>; Sun, 22 Sep 1996 11:54:29 -0700 (PDT)
Received: (from root@localhost) by lariat.lariat.org (8.8.Alpha.4/8.8.Alpha.4) id MAA10947; Sun, 22 Sep 1996 12:54:15 -0600 (MDT)
Date: Sun, 22 Sep 1996 12:54:15 -0600 (MDT)
From: Brett Glass <brett@lariat.org>
Message-Id: <199609221854.MAA10947@lariat.lariat.org>
To: brett@lariat.org, freebsd-questions@freebsd.org,
        pjchilds@imforei.apana.org.au
Subject: Re: systat/netstat utilities buggy?
Sender: owner-questions@freebsd.org
X-Loop: FreeBSD.org
Precedence: bulk

>  Grin.. better lock the kernel from opening/closing sockets during
>  a user-land program run?  Nah.. don't think so :)  

I agree. But at the very least one could make a quick copy of the
list rather than trying to traverse it in situ. (After all,
name resolution itself could alter the list, GUARANTEEING that
it would get messed up as it was scanned.) The kernel could provide
this as a service.

--Brett