Date: Fri, 11 Jul 2014 12:22:02 +0300 From: Konstantin Belousov <kostikbel@gmail.com> To: ports@freebsd.org Cc: Lee Howard <faxguy@howardsilvan.com>, hylafax-users@hylafax.org, Daren <daren.russell@ksm.co.uk> Subject: Re: [hylafax-users] Hylafax on FreeBSD 100% CPU Message-ID: <20140711092202.GZ93733@kib.kiev.ua> In-Reply-To: <53BF38D7.4030402@howardsilvan.com> References: <53B5329F.9000906@ksm.co.uk> <53B5F55A.20909@howardsilvan.com> <20140705103816.GP93733@kib.kiev.ua> <53B8601E.8040600@howardsilvan.com> <53BD1337.7040808@ksm.co.uk> <53BD9B43.5010604@howardsilvan.com> <53BE4EA9.5000308@ksm.co.uk> <20140710083923.GK93733@kib.kiev.ua> <53BF38D7.4030402@howardsilvan.com>
next in thread | previous in thread | raw e-mail | index | archive | help
--LioDbVBSbBewOkfJ Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable There was quite good and encouraging progress made on the state of the Hylafax for the FreeBSD, thanks to the efforts of Daren and Lee Howard. I do not know when the next release of Hylafax come out with the committed changes below, but whenever it happens, the port update to new release should improve things. The port accumulated quite a bit of problems, and most pressing issues on FreeBSD with the 100% CPU time spent on FIFO reads, as well as utmp->utmpx conversion, are fixed in upstream now. There is no maintainer for the Hylafax port, I am forwarding this message to ports@ in hope some motivated ports person will pick the stuff. My belief is that the programming issues are fixed, the remaining work is packaging-related. On Thu, Jul 10, 2014 at 06:07:35PM -0700, Lee Howard wrote: > On 07/10/2014 01:39 AM, Konstantin Belousov wrote: > > On Thu, Jul 10, 2014 at 09:28:25AM +0100, Daren wrote: > >> I had a quick go with your patch, but it didn't apply. Having a quick > >> look I believe it's simply an issue with the path to the hfaxd folder, > >> so I'll have another look as soon as I get a little time. I did also > >> have a quick look at compiling version 5.5.5 (at first without the > >> patch) but ran into issues straight away. When compiling GettyBSD.c++, > >> it's having a fatal error 'utmp.h' file not found. A quick google > >> suggests this was changed to "utmpx.h" in recent versions of FreeBSD a= nd > >> looking at the ports version of hylafax6, there's a few patches that > >> need applying for that to compile properly (and although I can see what > >> they do, I'm unsure why they do it!) I'll try and have another go when > >> I get a spare hour or two at work. > > This in fact means that FreeBSD port-specific patches should be upstrea= med. > > But the ports does not have a maintainer. Somebody needs to communicate > > the patches to the Hylafax developers. >=20 > I've taken what little of those patches seemed appropriate for upstream= =20 > application and I've committed them: >=20 > http://sourceforge.net/p/hylafax/HylaFAX+/2336/ > http://sourceforge.net/p/hylafax/HylaFAX+/2337/ >=20 > However, the real difference had to do with how the package in FreeBSD=20 > ports was being built: "--with-GETTY=3DSysV" instead of the "BSD" default= =20 > that would get picked-up normally. Since the SysVGetty supported utmpx= =20 > this worked. >=20 > Nonetheless, I've updated the BSDGetty code in HylaFAX+ to support=20 > utmpx. So it can now be built with SysV or BSD Getty support, as may be= =20 > desired. It seems to run fine with BSDGetty in my limited testing on a= =20 > FreeBSD 10 installation on a virtual machine using an iaxmodem. >=20 > http://sourceforge.net/p/hylafax/HylaFAX+/2339/ >=20 > Daren, since you seem to have a working solution it may not matter to=20 > you to mess around with any more testing. You would have some limited=20 > benefit in updating to HylaFAX+ code, but it may not be worth the effort= =20 > to you. If you can easily mimick the build and installation from=20 > FreeBSD ports, then updating should be no problem. But it seems that=20 > this may be a bit more struggle for you, and you may be happiest to just= =20 > remain with your working solution. I'll send you a tarball of the code=20 > separately - saving you the effort of patching. If you don't want to=20 > use it, that's understandable and fine. >=20 > If you (or anyone else) want to build and install HylaFAX+ on FreeBSD it= =20 > is this easy: >=20 > ./configure -with-LIBTIFF=3D"-L/usr/local/lib -ltiff"=20 > -with-TIFFINC=3D"-I/usr/local/include" && make && make install >=20 > If you want to use SysV Getty instead of BSD Getty, then change the=20 > configure command to: >=20 > ./configure -with-LIBTIFF=3D"-L/usr/local/lib -ltiff"=20 > -with-TIFFINC=3D"-I/usr/local/include" -with-GETTY=3DSysV >=20 > It may be more-involved if you want to get things going like JBIG and=20 > color fax support, etc. Someone interested should really volunteer to=20 > be the FreeBSD HylaFAX ports maintainer. >=20 > Thanks, >=20 > Lee. --LioDbVBSbBewOkfJ Content-Type: application/pgp-signature -----BEGIN PGP SIGNATURE----- Version: GnuPG v2 iQIcBAEBAgAGBQJTv6y5AAoJEJDCuSvBvK1B3tEP/3tlj6pvb5+sNaaH830+s6qn u0SXBDKObga0BxDUo8q//qt5wuO4BNTbGzdQ0/eawMZn3BZ/OEm4EvMhduGywNbj 60LH/rTSe5Fcb5TBtYWRZmzVaQptnEWaa7wLTsbUK6Hg2977RLMW03Q4muLgSCFx xNy+pLFh321cAfsO7ZPQMyk6GULM7Alhoi+23zDnjGt1xdET4LWT7271gCAswIAF xZfvwwgTRLAymMZxSAikRKDB8qKYAh/hY5VfPKPOntf19ZiyJZ1s6WcOYkuARNgA 14SM2QUjDIC7tfftdVCoJHExoH+HVnZKSLq+Y2N+ZJ+Z4ypEIM1tbUeROwnIunmU WqeaB29tDprWK0qNXeHlrDu4OEvtkbmehag7I2+E9a9yCbgPzOz0/MWJM2OvvIM0 cJsu5NkDRnENLoii1VqmM5Iw+pIvcnlsJjVz4h3uiJwlvm9a78tDlzbTO1ZmdbOV 4Nlk2Bno3OGWSaZzu096LcEpogzLXRONAbcyytDj9fYKvKQvhixRZvqP07yYgWf8 K8i5wGHAKSd6DQehtX41L90b9m9eynDVZFzs71sLl7M15bHO3MIE28O3s/MoQZfQ T9LWXsNQOMq1URdBkzF7+fqrt8GJnjPN0s6L1r3Q3A8lIKvYuYiMjlzx9A/yD5Bw NwUwg2ATrLFF9ZL+MkEY =LH8l -----END PGP SIGNATURE----- --LioDbVBSbBewOkfJ--
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20140711092202.GZ93733>