I just tried to duplicate the setup on our murder locally, and had no
success (The proxy timed out appropriately). Of course, our proxies are
on solaris...
I did see fud-client timeout before the server did when I couldn't resolve
the backend the server is on, but this isn't your problem if you a
Is there any hope somebody look at it ?
On Thu, Jun 05, 2003 at 11:28:35AM -0400, Etienne Goyer wrote:
> recvfrom() does not return when alarm() trigger. I am testing it on
> Linux RedHat 7.3, glibc 2.2.5.
>
> I am experiencing this problem when querying the fud daemon on the
> MUPDATE master
recvfrom() does not return when alarm() trigger. I am testing it on
Linux RedHat 7.3, glibc 2.2.5.
I am experiencing this problem when querying the fud daemon on the
MUPDATE master of Murder and the backend on which the queryed mailbox
reside does not have fud running. If you use fud-client t
On Wed, 4 Jun 2003, Etienne Goyer wrote:
> The fud daemon can proxy request for mailbox that are remote (ie
> Murder). In 2.1.13, the fud daemon will just sit there if the remote
> fud is not responding. It is strange because the recvfrom() is
> alarm()'ed; however, the SIGALRM handler do nothin
Just to let whoever know that this patch include two syslog() call that
I used to debug. I forgot to take them out before I made the patch.
They should be removed.
--
Etienne GoyerLinux Québec Technologies Inc.
http://www.LinuxQuebec.com [EMAIL PROTECTED]
Hi,
The fud daemon can proxy request for mailbox that are remote (ie
Murder). In 2.1.13, the fud daemon will just sit there if the remote
fud is not responding. It is strange because the recvfrom() is
alarm()'ed; however, the SIGALRM handler do nothing else than clear the
signal.
I am only a be
