Re: flexfax: aborting faxes

[Yves Trudeau <ytrudeau@jyrmatec.com>]

Nico Garcia wrote:
> 
> -----BEGIN PGP SIGNED MESSAGE-----
> 
> On Wed, 12 Nov 1997, Luiz Otavio L. Zorzella wrote:
> 
> > Hi,
> >
> > I'm trying to share my modem between hylafax and my pppd.
> >
> > I'm being able to do it using the "faxstate" command: I issue a
> > "faxstate -s busy" before I call pppd, so that hylafax won't mess with
> > my connection, and a "faxstate -s ready" after the pppd goes down, so
> > that the waiting faxes will be sent.
> >
> > My problem is that I'm trying to make this thing automatic (putting
> > this commands in my scripts), but I'm having problems when the pppd
> > trys to "go up", and hylafax is using the modem.
> 
> This should be unnecessary. HylaFAX and uucp and kermit and tip and
> minicom and pppd should all be looking in the same directory for the
> same style of lock files: this is /var/lock on Linux, /var/spool/locks
> on SunOS, etc.
> 
> Try running each program and seeing where and what kind of lock file it
> generates: these really should interoperate.
> 
>                         Nico Garcia

I have a similar problem to. I use v4.0pl1 on Linux 2.0.29. Everythings
works fine when hylafax is idle but if there is jobs in the sendq it's a
different story. I tried "faxstate cua1 -s down", "TimeOfDay:  
0500-0530" in config.cua1 (I need the modem between 5:00 and 5:00 AM)
and faxquit with no success. If faxgetty is no running on cua1, faxq
will in fact exit after the "faxquit" command... only after all the jobs
in sendq are done. We do a lot of broadcast faxing so there is always
jobs in sendq. I have already hack faxq in order to make it generate a
"faxq.pid" files which a can use to kill it but this means that the
current jobs will not be notified. Any input is greatly welcomed.

Yves Trudeau, Ph. D.
Jyrmatec Inc.
1381, Jolliet
Sherbrooke, Quebec
Canada, J1K 1Y8
Tel.:(819) 565-8349
Fax.:(819) 565-8273
email: ytrudeau@jyrmatec.com