Hylafax Mailing List Archives

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

Re: PATCH: hfaxd 4.0pl1 fixes for WHFC "syntax error" bug



Hi Alan.

I just tried to run the HylaFAX with your patch, but it seems that not only it not fix the wfhc bug, it also disabled hfaxd
from response to other clients (faxstat for example).

Sorry,

Uri

Alan Sparks wrote:

>  I just published the patch onto the mailing list.  I attach it (if you can
> deal with MIME attachments).
>
> You'll need a copy of the 'patch' program, unless you just want to look at
> the attached file and edit the two files by hand (not too bad).  The patch
> program is a GNU free program... let me know and I'll tell you where to get
> it if you don't have it.
>
> The patch is to two files in the hfaxd directory, Parser.c++ and
> HylaFaxServer.h.  After applying the patch, remake and install the rebuilt
> hfaxd and restart.
>
> What platform are you running on?  Sun, or another type of machine?
> -Alan
>
> -----Original Message-----
> From: Uri Shkolnik <uri@harmonic.co.il>
> To: Ulrich Eckhardt <uli@transcom.de>
> Cc: Alan Sparks <asparks@nss.harris.com>; flexfax@sgi.com <flexfax@sgi.com>
> Date: Monday, October 27, 1997 12:16 PM
> Subject: Re: flexfax: PATCH: hfaxd 4.0pl1 fixes for WHFC "syntax error" bug
>
> >I had looked for a solution for a long long time, I didn't know that it had
> been
> >found.
> >Can you specified the patch, where can I get it, and how to install it?.
> >
> >Thanks,
> >
> >Uri
> >
> >Ulrich Eckhardt wrote:
> >
> >> Alan Sparks wrote:
> >> >
> >> > Been testing this fix out for a few days, and it seems to work well.
> So
> >> > here it is.
> >> >
> >> > This patch to hfaxd fixes the occurrence of the "500 '': Syntax error,
> >> > expecting command token." error we've been fighting, using Hylafax
> 4.0pl1
> >> > and WHFC 0.x.  This patch is applied by going to your hfaxd directory,
> and
> >> > feeding the following (after "CUT HERE") to the "patch" utility.
> >> >
> >> > After watching the incoming stream from UNIX and NT clients, the
> problem
> >> > seems to localize in the getCmdLine() function of Parser.c++.  While
> the
> >> > command stream from UNIX clients appears continuous and unbroken, the
> >> > Windows client stream is sporadic and broken (odd Gates-ian flow
> control?).
> >> > Is broken flow triggers execution of the lines:
> >>
> >> Hi,
> >>
> >> is this really a bug of windows ? or is this a bug of HylaFAX.
> >> As i remember it's valid that not all data is sent at once.
> >> Here is an excerpt of the man page of the recv call :
> >>
> >>        The receive calls normally return any data avail­
> >>        able, up to the requested amount, rather than waiting  for
> >>        receipt  of  the  full  amount requested;
> >>
> >> Uli
> >> --
> >> Ulrich Eckhardt                            mailto:uli@transcom.de
> >> http://people.frankfurt.netsurf.de/uli
> >> Truly great madness can not be achieved without significant
> >> intelligence. (Henrik Tikkanen)
> >
> >
> >
>
>                                                   ------------------------------------------------------------------------
>
>                               Name: hfaxd-whfc-patch.pat
>    hfaxd-whfc-patch.pat       Type: unspecified type (application/octet-stream)
>                           Encoding: 7bit



Home
Report any problems to webmaster@hylafax.org

HylaFAX is a trademark of Silicon Graphics Corporation.
Internet connectivity for hylafax.org is provided by:
VirtuALL Private Host Services