Return to BSD News archive
Path: sserve!newshost.anu.edu.au!munnari.oz.au!news.Hawaii.Edu!ames!elroy.jpl.nasa.gov!swrinde!emory!dragon!rokkaku!kml Newsgroups: comp.os.386bsd.bugs Subject: Re: FIFOs cause lockup Message-ID: <C7L3rs.206@rokkaku.atl.ga.us> From: kml@rokkaku.atl.ga.us (Kevin Lahey) Date: Tue, 25 May 1993 13:21:27 GMT References: <C7DtDE.4A@rokkaku.atl.ga.us> <1993May24.064242.16966@email.tuwien.ac.at> Organization: Geeks-R-Us Lines: 21 In article <1993May24.064242.16966@email.tuwien.ac.at> mbirgmei@email.tuwien.ac.at (Martin BIRGMEIER) writes: >In article <C7DtDE.4A@rokkaku.atl.ga.us> kml@rokkaku.atl.ga.us (Kevin Lahey) writes: >[...] >>I rebuilt the kernel to support FIFOs using the 'options FIFO' line in the >>config file. It built fine, and the mkfifo command now works. The following >>sequence of commands will lock up the system: >> >[...] > >I once posted the following patch, although I don't know if it is correct: [Patch deleted.] Thanks! It worked great. I found that I needed to replace the PSOCK in the tsleep calls with PSOCK | PCATCH, so that the tsleep was interruptable. The software I was trying to get running needed to be able to get an alarm to get out of the open(2) call. Cheers, Kevin kml@rokkaku.atl.ga.us