faxrunq very broken on large queues

• Messages sorted by:[ date ][ thread ][ subject ][ author ]

Hi,

On Fri, Nov 27, 1998 at 11:00:38AM +0200, Graham Leggett wrote:
> > *Especially* if you have multiple modems, you shouldn't use faxrunq,
> > because it's locking/jobs distribution scheme is pretty lame - it was
> > never meant for that, and doesn't handle it well.
> 
> I hacked at the faxrunq shell script to try fix it, and came up with the
> attached script.

I'll look closely at it, and if it is really portable (which is one of the
major goals of the simple fax* scripts), I'll include it.

[Can't find an attachment...?]

> All it does is define a maximum number of faxrunq sessions that can run
> simultaneously, and uses a lock file to indicate if an instance is
> running. This will ensure that faxrunq can't run away if run too many
> times.

Yep.  But faxrunq still doesn't handle multiple fax lines too well - it
doesn't know about "modems", it has to check every job whether it's
already locked, etc.

> > Faxrunqd needs Perl5, runs all the time, and was written for a customer
> > that sends about 1000 faxes a day over 5 modem lines, all during business
> > hours (10:00-17:00).  It works for them very smoothly since day 1...
> 
> Will give this a try.

Let me hear about your experiences :)

gert


-- 
USENET is *not* the non-clickable part of WWW!
                                                           //www.muc.de/~gert/
Gert Doering - Munich, Germany                             gert@greenie.muc.de
fax: +49-89-35655025                        gert.doering@physik.tu-muenchen.de