HylaFAX The world's most advanced open source fax server

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

possible bug in faxcron



Faxcron is supposed to return the associated trace log of any calls
that failed suspiciously.

It never worked for me.  

I looked into why and found this answer:

If I modified the awk script in faxcron script as follows:
making the failures have a first letter capital (as they do in 
the etc/xferlog), then it worked fine.

I use:  Gnu Awk (gawk) 3.0, patchlevel 0

I am curious if anyone can confirm, deny , or clarify.

Thanks,
  Seth Chaiklin

Here is a small patch.

--- faxcron.sh.in.orig	Fri Mar 20 12:32:44 1998
+++ faxcron.sh.in	Fri Mar 20 16:15:10 1998
@@ -229,14 +233,14 @@
 }
 
 BEGIN		{ FS="\t";
-		  callFailed["busy signal"] = 1;
-		  callFailed["unknown pro"] = 1;
-		  callFailed["no carrier "] = 1;
-		  callFailed["no local di"] = 1;
-		  callFailed["no answer f"] = 1;
-		  callFailed["job aborted"] = 1;
-		  callFailed["invalid dia"] = 1;
-		  callFailed["can not loc"] = 1;
+		  callFailed["Busy signal"] = 1;
+		  callFailed["Unknown pro"] = 1;
+		  callFailed["No carrier "] = 1;
+		  callFailed["No local di"] = 1;
+		  callFailed["No answer f"] = 1;
+		  callFailed["Job aborted"] = 1;
+		  callFailed["Invalid dia"] = 1;
+		  callFailed["Can not loc"] = 1;
 		  months["01"] = "Jan"; months["02"] = "Feb";
 		  months["03"] = "Mar"; months["04"] = "Apr";
 		  months["05"] = "May"; months["06"] = "Jun";




Project hosted by iFAX Solutions