Hylafax Mailing List Archives
|
[Date Prev][Date Next][Thread Prev][Thread Next]
[Date Index]
[Thread Index]
Re: [hylafax-users] notify
Lee Howard typed (on Tue, May 03, 2005 at 04:34:31PM -0700):
| Jean-Pierre Radley wrote:
|
| >Well, I'm getting these errors:
| >
| > bin/notify "doneq/q111076" "failed" "1:30"
| > mawk: line 37: regular expression compile failed (missing
| > operand)
| > *
| > printf: : Invalid argument (error 22)
| > printf: : Invalid argument (error 22)
| > printf: : Invalid argument (error 22)
| > No recipient addresses found in header
| >
| >If I change setup.cache to use awk instead of mawk:
| >
| > awk: error compiling regular expression /*/: *?+ not preceded by
| > valid
| > expression
| > source line 37 of program <<
| > function p(var ... >>
| > context is
| > >>> gsub("*","",status) <<< ;
| > printf: : Invalid argument (error 22)
| > printf: : Invalid argument (error 22)
| > printf: : Invalid argument (error 22)
| > No recipient addresses found in header
| >
| >I can't figure out which line 37 of which file. :-(
| >
| >Exactly the same binary of mawk is running on my sites that do send
| >notifications as on the problem site where I'm getting those errors.
| >
| >
| >
|
| Someone else asked about this same problem here yesterday or Friday.
| You may want to check the recent archives.
|
| The suggestion is to upgrade to current CVS HEAD, as we think we got it
| fixed. I can't locate the Bugzilla report quickly, it seems.
Ok, the latest CVS variant did fix it; it was broken some time after
4.1.8.
Is it possible, please. for CVS downloads to bear changing Version
strings?
The binaries I just built from the latest source code still bear "4.2.1"
inside the binary. It would also be nice to have a flag to display the
version for any or all of the Hylafax binaries, instead of having to run
the "strings" command.
--
JP
____________________ 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*