![]() |
Tim Rice wrote: On Mon, 1 Jun 1998, Jim Whitby wrote: > David Woolley wrote: > > > > > Anyone have any suggestions? > > > More info required, please, let me know. > > > > Leave it at its current priority - the actual fax protocol is very > > time critical. > > Normaly I would, but *anything* that requires 100% cpu time is too much. > For a maichne that is idling at less that 5% to jump to 100% and not be > doing anything is too much priority. > It's not a priority issue. It's correctly set to run at "Fixed Class" priority. Are you on UnixWare 2.1.3? I just upgraded to 2.1.3 and now my faxgetty takes 50% of the available CPU time as reported by "ps -A -ouser,pid,ppid,pcpu,vsz,time,tty,args". Truss(1) shows pages of read(1, 0x080473DC, 2047) = 0 poll(0x08045BC4, 2, -1) = 1 read(1, 0x080473DC, 2047) = 0 poll(0x08045BC4, 2, -1) = 1 read(1, 0x080473DC, 2047) = 0 poll(0x08045BC4, 2, -1) = 1 looks like the common CONFIG_OPENFIFO problem (but never saw this in faxgetty(1M) before); what is fd 1 for a file? matthias With faxgetty running rtpm(1M) shows CPU: 100 %u+s 0 %w+i 54 %usr 46 %sys 0 %wio 0 %idl With no faxgetty. CPU: 1 %u+s 99 %w+i 1 %usr 0 %sys 0 %wio 99 %idl I hate it when OS upgrades break things. It worked good on 2.1.2 I'm going to recompile HylaFAX from scratch to see if that makes any difference. -- Tim Rice Multitalents (707) 887-1469 (voice) tim@trr.metro.net