|
Hylafax Mailing List Archives
|
[Date Prev][Date Next][Thread Prev][Thread Next]
[Date Index]
[Thread Index]
Re: RE>Problem with fax receiving
On 19 Feb 1999, Michael Firkins wrote:
> RE>flexfax: Problem with fax receiving
> 19/2/99
> Hi.
> I can't really help you with hylafax receiving, but I can explain why cu
> works with mgetty and not faxgetty. It is to do with the way they are
> structured:
>
> mgetty does not hold the lock on the port. It waits there and watches
> for valid data "RING" etc and then takes it and sets a lock. This means
> that other programs, (minicom, cu, pppd etc) can pick up the port and
> lock it (except when mgetty is actively using it or resetting it after
> a session).
>
> Faxgetty on the other hand sets a lock when it is invoked from inittab
> and there it stays. Hylafax owns that port and you would have to kill
^^^^
> off faxgetty to get the port back so that cu can access it.
^^^^^^^^^^^^
That's not so. If HylaFAX is configured correctly, cu & uucico work
just fine while faxgetty is running.
All the programs need to use the same lockfile name and the same
type of lockfile.
>
> Good luck,
>
> Michael
> --------------------------------------
> Date: 19/2/99 8:05 AM
> To: Michael Firkins
> From: Alex Povolotsky
> Hello!
>
> I'm trying to set up fax receiving using a _VERY_ good Class2 modem. It
> works
> just fine with mgetty, but all my efforts to set it up with faxgetty
> fails.
>
> I've tried every combination of speed and flow control I could invent
> (19200,
> 38400 and 57600, with soft, hard and no flow for 19200, soft and hard
> for
> 38400) but always gets Missing EOL in 5 seconds.
>
> For some unknown reason, cu fails to work with modem _TOGETHER_ with
> faxgetty.
> Together with mgetty it works just fine.
>
> Setup strings for mgetty and faxgetty looks identical.
>
> I'm using latest hylafax (4.0pl2).
>
> What should I test? What should I look at? Please help.
>
> Alex.
>
--
Tim Rice Multitalents (707) 887-1469 (voice)
tim@trr.metro.net
