Date: Mon, 26 Jan 1998 05:20:32 -0600 From: Randy Terbush <randy@covalent.net> To: dyson@FreeBSD.ORG Cc: brian@worldcontrol.com, current@FreeBSD.ORG Subject: Re: Cyclades/Hylafax/SMP select problems? Message-ID: <19980126052032B.randy@covalent.net> In-Reply-To: Your message of "Mon, 26 Jan 1998 05:14:28 -0500 (EST)" <199801261014.FAA00431@dyson.iquest.net> References: <199801261014.FAA00431@dyson.iquest.net>
next in thread | previous in thread | raw e-mail | index | archive | help
"John S. Dyson" <dyson@FreeBSD.ORG> wrote: > > > The Hylafax faxgetty and faxq processes spin out of control > > > chewing up nearly 100% CPU. The same configuration ran without > > > problems on a single P5 machine running 2.2-STABLE. > > > > > > As I begin to dig deeper into this, are there any know problems > > > with this mix? > > > > Just thought you'd like to know you are not alone. faxq on > > my SMP system does the same thing. > > > Sometimes the output of ktrace or truss can be useful. Also the > contents of /proc/<pid>/map sometimes helps with hints as to > what is going on. Seems that a change to open the FIFO O_RDWR solves the problem. Apparently, select() is returning when it should not be. This must be a new bug in select().
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?19980126052032B.randy>