Date: Mon, 26 Jan 1998 00:53:56 -0800 From: brian@worldcontrol.com To: Amancio Hasty <hasty@rah.star-gate.com>, brian@worldcontrol.com Cc: Randy Terbush <randy@covalent.net>, current@FreeBSD.ORG Subject: Re: Cyclades/Hylafax/SMP select problems? Message-ID: <19980126005356.16731@top.worldcontrol.com> In-Reply-To: <199801260824.AAA02827@rah.star-gate.com>; from Amancio Hasty on Mon, Jan 26, 1998 at 12:24:27AM -0800 References: <19980126001331.05717@top.worldcontrol.com> <199801260824.AAA02827@rah.star-gate.com>
next in thread | previous in thread | raw e-mail | index | archive | help
> > On %M %N, Randy Terbush <randy@covalent.net> wrote: > > > The Hylafax faxgetty and faxq processes spin out of control > > > chewing up nearly 100% CPU. Brian Litzinger <brian@worldcontrol.com> wrote: > > Just thought you'd like to know you are not alone. faxq on > > my SMP system does the same thing. On %M %N, Amancio Hasty <hasty@rah.star-gate.com> wrote: > Any clues as to where is spending its time?? The program gives no clues. Regretably it seems to perpetually be in the RUN state. However, I have a guess. I suspect that a select (poll?) call is returning with nothing set. The program is getting into an infinite loop calling select. I've found that the program does work. It is just consuming 100% of 1 CPU. I believe the problem is not SMP related. I.E. it will happen in uni-processor mode too. -- Brian Litzinger <brian@worldcontrol.com>
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?19980126005356.16731>