> 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
