Re: R: flexfax: WHFC send/receive prob

[Nico Kadel-Garcia <raoul@cirl.meei.harvard.edu>]

-----BEGIN PGP SIGNED MESSAGE-----

On Tue, 26 Oct 1999, Stefano Giro wrote:

> Date: Tue, 26 Oct 1999 08:37:38 +0200
> From: Stefano Giro <stefano.giro@msg.it>
> To: jgrald@bestweb.net, flexfax@sgi.com
> Subject: R: flexfax: WHFC send/receive prob
> 
> Try with /dev/cua0 device.
> 
> Stefano Giro
> steno@msg.it

Bad, bad, bad idea. RedHat 6.0 and later no longer use /dev/cua* if
avoidable. Those devices are a remnant of the use of "split device"
tricks, where one program would sit on /dev/ttyS0 and handle incoming
calls and the other would sit on /dev/cua0 and do outgoing and have
file-locking in /var/lock/*. HylaFAX, and mgetty both handle this
handshaking stuff correctly to interact on a single line with other
programs such as minicom, kermit, and uucp.

> > I have installed hylafax 4.1beta1 on RedHat 6.1 and am using the
> > WHFC client.  My problem is if I run faxgetty ttyS0, then WHFC doesn't
> send
> > faxes to the queue (and has no error messages).  If I just run faxmodem
> ttyS0
> > then WHFC works fine, but I cannot receive faxes.  I have checked the
> documentation,
> > read the WHFC faq, but I must be missing something.  Any ideas?

Something is strange here: is there a /dev/modem or /dev/cua0 with another
process sitting on it? Another fax program, maybe?

			Nico Kadel-Garcia
			Senior Engineer, CIRL 
			Mass. Eye and Ear Infirmary
			raoul@cirl.meei.harvard.edu

-----BEGIN PGP SIGNATURE-----
Version: 2.6.2

iQCVAwUBOBWo/j/+ItycgIJRAQE6wAQAnhyUc/W8119O4QVz7KwxC4mO9ymtVJfg
oivUCk9/HoFWdCyNmZ0vwmPIHLaeNOPS26id5vSb5Yhns9YDnDbQoSRQSOO/k8hq
O60BV43MQ8w5LhOMsz/zbu4JrLLgyOe9zl35fxTaXYfR5XdaO0e3FGF18djrrAoQ
vYDapLk1m1A=
=FCn/
-----END PGP SIGNATURE-----