From owner-freebsd-ports Thu Jun 29 10:25:54 2000 Delivered-To: freebsd-ports@freebsd.org Received: from gw-nl1.origin-it.com (gw-nl1.origin-it.com [193.79.128.34]) by hub.freebsd.org (Postfix) with ESMTP id 46A2537C08A for ; Thu, 29 Jun 2000 10:25:43 -0700 (PDT) (envelope-from Helge.Oldach@de.origin-it.com) Received: from mail.de.origin-it.com (localhost.origin-it.com [127.0.0.1]) by gw-nl1.origin-it.com with ESMTP id TAA19874; Thu, 29 Jun 2000 19:25:39 +0200 (MEST) (envelope-from Helge.Oldach@de.origin-it.com) Received: from smtprelay-de1.origin-it.com(172.16.188.53) by gw-nl1.origin-it.com via mwrap (4.0a) id xma019872; Thu, 29 Jun 00 19:25:39 +0200 Received: from mailhub.de.origin-it.com ([130.143.166.88]) by mail.de.origin-it.com (8.9.3/8.8.5-1.2.2m-19990317) with ESMTP id TAA26753; Thu, 29 Jun 2000 19:25:38 +0200 (MET DST) Received: from galaxy.de.cp.philips.com (galaxy.de.cp.philips.com [130.143.166.29]) by mailhub.de.origin-it.com (8.9.3/8.9.3/hmo01feb00) with ESMTP id TAA64455; Thu, 29 Jun 2000 19:25:37 +0200 (CEST) (envelope-from Helge.Oldach@de.origin-it.com) Received: (from hmo@localhost) by galaxy.de.cp.philips.com (8.9.3/8.9.3/hmo14aug98) id TAA28736; Thu, 29 Jun 2000 19:25:36 +0200 (MET DST) Message-Id: <200006291725.TAA28736@galaxy.de.cp.philips.com> Subject: Re: "No response to MPS or EOP" problem? To: hylafax-users@hylafax.org Date: Thu, 29 Jun 2000 19:25:36 +0200 (MET DST) Cc: ports@FreeBSD.org From: Helge Oldach X-Address: ORIGIN Deutschland GmbH, Billstrasse 80, D-20539 Hamburg, Germany X-Phone: +49 40 7886 464, Fax: +49 40 7886 235, Mobile: +49 172 4515513 X-NCC-RegID: de.origin MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-ports@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Folks, recently the FreeBSD port was upgraded to hylafax 4.1beta2. I upgraded and ran into this well-known problem. It turned out that the UUCP lock files are not being properly written, so that faxgetty thought the line was free while in fact there was a fax being sent out. Faxgetty jumped right into the ongoing conversation, like in the following log fragment: Jun 29 17:32:30.39: [49268]: <-- data [256] Jun 29 17:32:30.39: [49268]: SENT 4351 bytes of data Jun 29 17:32:30.39: [49268]: SEND 2D RTC Jun 29 17:32:30.39: [49268]: <-- data [30] Jun 29 17:32:30.39: [49268]: <-- data [2] Jun 29 17:32:30.39: [49268]: SEND end page Jun 29 17:32:37.65: [49268]: --> [14:ATE0V1Q0S0=0H0] <---- EEEEK!!!! Jun 29 17:32:37.65: [49268]: --> [2:OK] Jun 29 17:32:37.65: [49268]: DELAY 95 ms Jun 29 17:32:37.76: [49268]: SEND send EOP (no more pages or documents) Jun 29 17:32:37.76: [49268]: <-- [9:AT+FTH=3\r] Jun 29 17:32:40.32: [49268]: --> [0:] Jun 29 17:32:40.32: [49268]: SEND send EOP (no more pages or documents) Jun 29 17:32:40.32: [49268]: <-- [9:AT+FTH=3\r] Jun 29 17:32:40.35: [49268]: --> [5:ERROR] At one instance I observed a lockfile containing exactly: 59\0\0\0\0 (that is, five spaces, '5', '9', and four NUL characters). The size was right (11 characters), but the contents was nonsense. This tiny patch cured the problem: -------------------------------------------------------------------------------- --- faxd/UUCPLock.c++.ORIG Wed Jun 28 22:13:29 2000 +++ faxd/UUCPLock.c++ Thu Jun 29 18:38:41 2000 @@ -315,7 +315,7 @@ AsciiUUCPLock::setPID(pid_t pid) { // XXX should this be %d or %ld? depends on pid_t - snprintf((char*) data, sizeof(data), "%*d\n", UUCP_PIDDIGITS, pid); + snprintf((char*) data, UUCP_PIDDIGITS+2, "%*d\n", UUCP_PIDDIGITS, pid); } bool -------------------------------------------------------------------------------- Hope this is of help for somebody. Regards, Helge N.B. hylafax 4.0PL2 does *not* show this behaviour as it doesn't use snprintf but sprintf. So if you still use 4.0, this isn't for you. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-ports" in the body of the message