HylaFAX The world's most advanced open source fax server

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

Re: [hylafax-users] Problems with hylafax regarding job files without number and/or gnu.hylafax class



> -----Original Message-----
> From: Lee Howard [mailto:faxguy@xxxxxxxxxxxxxxxx]
> Sent: 02/10/2005 12:26 PM
> To: Ulf Zimmermann
> Cc: hylafax-users@xxxxxxxxxxx
> Subject: Re: [hylafax-users] Problems with hylafax regarding job files
> without number and/or gnu.hylafax class
> 
> On 2005.02.10 12:18 Ulf Zimmermann wrote:
> > I did some investigation further into this after I sent this
message.
> > It
> > looks like gnu.hylafax has been submitting jobs in this form since
> > forever (one job with just document and then another job with number
> > and
> > reusing the document). But only since last Monday hylafax has been
> > logging all these "Null or missing number".
> 
> A client *can validly* reuse uploaded documents.  I'm not sure though
> why it would suddenly fail for you, though.  What else happened on
last
> Monday?
> 
> Lee.

Ok, I know now where the messages come from. So as said above,
gnu.hylafax creates two requests, one without number. It stay a while
around (I think without config, as job submitted 3 hours or 4 hours).
The actual entry sent to syslog comes from "faxstat -s" being run, which
cans the queue. As I wrote a little program which relies on "faxstat -s"
being called every 5 seconds, I started to have the logentries. We do
about 800-1,200 pages a day or about 500-600 faxes, that adds up.

Time to ask our java programmers to look at either gnu.hylafax 0.0.8
(which has a new interface and requires our application to be changed)
or look at 0.0.7 not to submit two jobs.

Ulf.



____________________ HylaFAX(tm) Users Mailing List _______________________
  To subscribe/unsubscribe, click http://lists.hylafax.org/cgi-bin/lsg2.cgi
 On UNIX: mail -s unsubscribe hylafax-users-request@xxxxxxxxxxx < /dev/null
  *To learn about commercial HylaFAX(tm) support, mail sales@xxxxxxxxx*




Project hosted by iFAX Solutions