Summary: | High CPU Utilization on HylaFAX processes | ||||||
---|---|---|---|---|---|---|---|
Product: | Base System | Reporter: | ruanchunping | ||||
Component: | kern | Assignee: | freebsd-bugs (Nobody) <bugs> | ||||
Status: | Closed Overcome By Events | ||||||
Severity: | Affects Only Me | CC: | moiseev, ports, rene | ||||
Priority: | Normal | ||||||
Version: | Unspecified | ||||||
Hardware: | Any | ||||||
OS: | Any | ||||||
Attachments: |
|
Description
ruanchunping
2013-11-06 14:30:00 UTC
Created attachment 149713 [details]
Patch for comms/hylafax port.
It is actually comms/hylafax bug, not the kernel bug.
The releaseAtLeast() function in the configure script compares OS version as a string, and that is wrong.
# expr 9.3-RELEASE \>= 3.0
1
# expr 10.1-RELEASE \>= 3.0
0
As a result, hylafax is building without CONFIG_OPENFIFO="O_RDWR".
(In reply to Alexander Moisseev from comment #1) > Created attachment 149713 [details] > Patch for comms/hylafax port. > > It is actually comms/hylafax bug, not the kernel bug. > > The releaseAtLeast() function in the configure script compares OS version as > a string, and that is wrong. > > # expr 9.3-RELEASE \>= 3.0 > 1 > # expr 10.1-RELEASE \>= 3.0 > 0 > > As a result, hylafax is building without CONFIG_OPENFIFO="O_RDWR". Thanks for your help. I setup a jail (8.2 world with 10-STABLE kernel) to run hylafax, it works very well for 1 year. For bugs matching the following conditions: - Status == In Progress - Assignee == "bugs@FreeBSD.org" - Last Modified Year <= 2017 Do - Set Status to "Open" This port expired today, and upstream is long gone. |