From owner-freebsd-questions  Tue Aug  6 12:45:43 1996
Return-Path: owner-questions
Received: (from root@localhost)
          by freefall.freebsd.org (8.7.5/8.7.3) id MAA15464
          for questions-outgoing; Tue, 6 Aug 1996 12:45:43 -0700 (PDT)
Received: from pelican.altadena.net (pelican.dial.interworld.net [206.124.240.237])
          by freefall.freebsd.org (8.7.5/8.7.3) with SMTP id MAA15458
          for <questions@freebsd.org>; Tue, 6 Aug 1996 12:45:41 -0700 (PDT)
Received: by pelican.altadena.net (Smail3.1.29.1 #10)
	id m0uns4K-0000RhC; Tue, 6 Aug 96 12:45 PDT
Message-Id: <m0uns4K-0000RhC@pelican.altadena.net>
From: pete@pelican.altadena.net (Pete Carah)
Subject: hylafax died
To: questions@freebsd.org
Date: Tue, 6 Aug 1996 12:45:31 -0700 (PDT)
X-Mailer: ELM [version 2.4 PL23]
Content-Type: text
Sender: owner-questions@freebsd.org
X-Loop: FreeBSD.org
Precedence: bulk

We had hylafax working fine in 2.0.5R as updated to various -stable
releases; on upgrading to (binary) 2.1.5R faxq ceased its job.
It is still running and can find the queue directory.  faxstat, faxd.recv,
and pagesend/sendpage all work fine (we mainly use hylafax for paging, only
occasionally fax's).

Has something been done in 2.1.5R that wasn't in the last June 2.1-stable
snapshot to break faxq?  I know about the locking bug in faxq that makes
it break if there are too many expired jobs in the queue...

Thanks in advance,

-- Pete