[Top][All Lists]
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: Another 4.0 problem!
From: |
Jan-Henrik Haukeland |
Subject: |
Re: Another 4.0 problem! |
Date: |
Thu, 18 Sep 2003 19:43:33 +0200 |
User-agent: |
Gnus/5.1002 (Gnus v5.10.2) XEmacs/21.4 (Reasonable Discussion, linux) |
Christian Hopp <address@hidden> writes:
> The monit CLI interface doesn't behave correctly... in SSL and nonSSL.
> Monit is neither starting or stopping an app. The status is done locally
> and monit is often complaining "The monit server did not return a process,
> device, file, directory or host record." => Socket connection is
> successful... but unknown data has been received.
>
> In most case monit does receive 0 bytes from the http server. Sometimes it
> just does local status.
Aha, damnit, I just browsed through processor.c and I can see that we
are using standard file i/o via a FILE variable. Using a buffering
FILE is a sure reciept for disaster when non-blocking i/o is used.
I have changed FILE to be unbuffered, this is a hack and may work. But
in the long run (next release) we must change i/o to use the
socket_read and socket_write methods.
Christan can you please report if this hack work, or not?
--
Jan-Henrik Haukeland