Date: Fri, 18 Feb 2000 15:59:43 +0100 From: Poul-Henning Kamp <phk@critter.freebsd.dk> To: Thomas Stromberg <tstromberg@rtci.com> Cc: freebsd-current@FreeBSD.ORG Subject: Re: repost of procfs crashes in -CURRENT (no html).. Message-ID: <3736.950885983@critter.freebsd.dk> In-Reply-To: Your message of "Fri, 18 Feb 2000 09:56:50 EST." <Pine.GSO.4.20.0002180947420.28433-100000@barracuda.aquarium.rtci.com>
next in thread | previous in thread | raw e-mail | index | archive | help
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 <Pine.GSO.4.20.0002180947420.28433-100000@barracuda.aquarium.rtci.com>, Thomas Stromberg writes: >3 users. One with X running <me>, and two users running breakwidgets ><binary testing script>, 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
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?3736.950885983>