From owner-freebsd-current Fri Feb 18 6:59:56 2000 Delivered-To: freebsd-current@freebsd.org Received: from critter.freebsd.dk (critter.freebsd.dk [212.242.40.131]) by hub.freebsd.org (Postfix) with ESMTP id D6F4E37B988 for ; Fri, 18 Feb 2000 06:59:51 -0800 (PST) (envelope-from phk@critter.freebsd.dk) Received: from critter.freebsd.dk (localhost.freebsd.dk [127.0.0.1]) by critter.freebsd.dk (8.9.3/8.9.3) with ESMTP id PAA03738; Fri, 18 Feb 2000 15:59:43 +0100 (CET) (envelope-from phk@critter.freebsd.dk) To: Thomas Stromberg Cc: freebsd-current@FreeBSD.ORG Subject: Re: repost of procfs crashes in -CURRENT (no html).. In-reply-to: Your message of "Fri, 18 Feb 2000 09:56:50 EST." Date: Fri, 18 Feb 2000 15:59:43 +0100 Message-ID: <3736.950885983@critter.freebsd.dk> From: Poul-Henning Kamp Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG The real solution is to make killall(1)s funtionality part of kill(1) and avoid reading /proc so that we don't even have to mount /proc. Poul-Henning In message , Thomas Stromberg writes: >3 users. One with X running , and two users running breakwidgets >, which make use of a minimized version of the >"killall" perl script which reads procfs. > >This crash appears to be the old one where when two processes read procfs >simultaneously, ugly things can happen. -- Poul-Henning Kamp FreeBSD coreteam member phk@FreeBSD.ORG "Real hackers run -current on their laptop." FreeBSD -- It will take a long time before progress goes too far! To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message