From mboxrd@z Thu Jan 1 00:00:00 1970 From: erik quanstrom Date: Wed, 26 Mar 2014 15:13:50 -0400 To: 9fans@9fans.net Message-ID: <2e616d063ebde1c9d56818fa0f789f0e@chula.quanstro.net> In-Reply-To: <53331BD0.8050903@mail.com> References: <53311910.5090307@mail.com> <53320D1C.2050502@mail.com> <53331BD0.8050903@mail.com> MIME-Version: 1.0 Content-Type: text/plain; charset="US-ASCII" Content-Transfer-Encoding: 7bit Subject: Re: [9fans] No regression tests Topicbox-Message-UUID: d1d07dc2-ead8-11e9-9d60-3106f5b1d025 > Here mount /srv/bcscan /n/bc gives a readable /n/bc/bcU0/data. > > Then the reader is unplugged > > bootes 12 0:00 0:00 336K Pread bcscan > bootes 13 0:00 0:00 336K Rendez bcscan > bootes 14 0:00 0:00 336K Rendez bcscan > > Plaese note that here we see a different case. There are three > spurious processes. On the plant (same test) there is only one. > > Then the reader is plugged in again > > bootes 13 0:00 0:00 336K Rendez bcscan > bootes 14 0:00 0:00 336K Rendez bcscan > bootes 432 0:00 0:00 336K Rendez bcscan > bootes 434 0:00 0:00 336K Pread bcscan > bootes 435 0:00 0:00 336K Rendez bcscan > bootes 436 0:00 0:00 336K Rendez bcscan > bootes 437 0:00 0:00 336K Open bcscan i should learn chess so i don't ask questions in serial. with acid, you can get a backtrace of process 12 and get the fd it is reading. /proc/12/fd should have the file descriptor bcscan thinks is open. if it also, since process 13 and 14 did not wake from rendezvous, there is a second issue. maybe you can see how 12 could exit and leave 13 and 14 hanging. - erik