Hylafax Mailing List Archives

[Date Prev][Date Next][Thread Prev][Thread Next] [Date Index] [Thread Index]

Re: faxgetty & pppd



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

On Fri, 30 Jan 1998, Dave Gibbs wrote:

> I'm really happy with hylafax so far, excellent package, but I'm a bit
> confused about the situation with faxgetty and pppd.
> 
> I understand the situation with inbound support, faxgetty 'handing over'
> to mgetty whenever necessary, but it's outbound I have a problem with.
> 
> If I enable faxgetty in my inittab, as :-
> 
> fx:345:respawn:/usr/local/sbin/faxgetty cua1
> 
> all works fine on receiving faxes.  However, when I try to use pppd to
> dial out on the same port, obviously I get the message :-
> 
> Jan 30 09:02:18 zack pppd[1049]: Failed to open /dev/cua1: Device or
> resource busy
> 
> Now, what is the correct mechanism for combining these two so I can dial
> out while faxgetty is not actually answering a fax?

Take a look at my page for SunOS at
http://cirl.harvard.edu/~raoul/INSTALL-sunos4.1.x-v4.0pl1.html

mgetty, HylaFAX, kermit, tip, cu, minicom, seyon, PPP, etc. all have
to agree on where the locking files live and what format they are in.
This depends not only on the OS but on which *version* of the OS,
especially for Linux.

Under SunOS, they are ASCII files in the directory /var/spool/locks, and
they all have to refer to the same names for the modems.


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

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

iQCVAwUBNNJw9j/+ItycgIJRAQFGwgP/S5w8Yg4qHi1rpAKZPLf5XnrNUuFZRW4r
d777AsjgJpN9cLVtsV3ZjjqVA2kgIH6PbTICWnPtF8uFDa65QoSVOohbMluNeW+V
RXIQlGA3DB7h0BjLndKw228XJ3TL1pfNnvotO/iwDzyqfTwxJMr/xdaGR4vVbh0C
e1RYK4kd6hg=
=iwKG
-----END PGP SIGNATURE-----



Home
Report any problems to webmaster@hylafax.org

HylaFAX is a trademark of Silicon Graphics Corporation.
Internet connectivity for hylafax.org is provided by:
VirtuALL Private Host Services