Hylafax Mailing List Archives
|
[Date Prev][Date Next][Thread Prev][Thread Next]
[Date Index]
[Thread Index]
Re: faxgetty conflicts with ppp and minicon
-----BEGIN PGP SIGNED MESSAGE-----
On Mon, 9 Mar 1998 jlb@ordata.com wrote:
> Mattew Rice suggested I mail my trouble to the mailing list. I have
> read the archive concerning the previous reports and tried to
> implement the fixes. Nothing seems to work. Minicom and faxgetty
> both are set to use /var/lock as their lock directories. Even when
> minicom creates both lock files faxgetty continues to get after the
> /dev/ttyE0 and /dev/modem. Neither program reports the device
> locked. The Stallion EasyIO-8 board has generally functioned well in
> both SCO 3.2v4.1 and Linux 2.0.29 with minicom or ppp-on in the
> latter and ecu and uucp in the former.
> The box is a 486DX-50 with Ultrastor 34F, Cirrus Logic video, and the
> Stallion EasyIO-8. No IDE or soundcard devices. If I kill faxgetty
> and comment out the inittab entry for the faxgetty, the other
> programs work.
Which version of HylaFAX are you using, and did you compile *HylaFAX*
to use /var/lock with ascii or binary lock files as appropriate to your
software?
Remember also: all these devices have to be configured to use the same
lock files and tty lines to interact. This means you cannot use
/dev/ttyE0 in one place, /dev/modem in another, and expect them to
interact correctly.
Nico Garcia
Engineer, CIRL
Mass. Eye and Ear Infirmary
raoul@cirl.meei.harvard.edu
-----BEGIN PGP SIGNATURE-----
Version: 2.6.2
iQCVAwUBNQSkZj/+ItycgIJRAQE0ZgP/YB5IB0JvdIZTNssiPOu3FDe7A4sqWmlA
bK0i0L3laSmggMtQlCLwMbzJ2687u8093luIhsxTVaD1IpZpIxFOfQ0nG/DeVBH0
1J5PNKyNQR9Pzt0IS+nmeUdKl2JIeR/+++GduO1APTzNELsHRX5EBGMRGf8Q7/mZ
P3U4leKaimk=
=8PL0
-----END PGP SIGNATURE-----