![]() |
So to clarify (myself): 1) FaxNotify is not mandatory for hylafax 5.2.6 (OK, I haven't) 2) there is a little patch for notify version 5.2.6 (tomorrow I will try. local time: 23.50 !) 3) faxsetup should be run after upgrading / installing ( I did it always on upgrade ) The only question I was not anwered is the following: OK, FaxNotify is not mandatory. BUT if I do have a FaxAccounting script, which run after each xferfaxlog entry is written, is it possible that this presence alter the notify process ? Is there any chance removing FaxAccounting makes notify starts working again ? Andrea -----Messaggio originale----- Da: hylafax-users-bounce@xxxxxxxxxxx [mailto:hylafax-users-bounce@xxxxxxxxxxx] Per conto di Lee Howard Inviato: martedì 29 luglio 2008 23.17 A: Glen Batchelor Cc: hylafax-users@xxxxxxxxxxx Oggetto: Re: [hylafax-users] R: problem with notify Glen Batchelor wrote: > The -D option for sendfax _is_ working with the > symlink for ./etc under ./bin, but it's repeatedly sending notices for the > same queue files that were successfully sent for a single fax job. There was a bug introduced into notify in 5.2.6. Please examine the one-line change to notify here: http://hylafax.cvs.sourceforge.net/hylafax/hylafax/util/notify.sh.in?r1=1.39&r2=1.40&view=patch ... and apply it to your bin/notify file. See if that helps at all. However, other people have been commenting on this thread about versions prior to 5.2.6, and this does not relate to those. Thanks, Lee. ____________________ 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* ____________________ 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*