sigh, after further testing i realized it was something else. yes, the
failover works fine if the mount isn't there. thanks for your help.
i do have one question tho - what happens to qmail-local processes that are
in the middle of delivery when the mount goes down? will they block until
the mount is back up?
thanks-
shag
=====
Judd Bourgeois | CNM Network +1 (805) 520-7170
Software Architect | 1900 Los Angeles Avenue, 2nd Floor
[EMAIL PROTECTED] | Simi Valley, CA 93065
To ignore evil is to become an accomplice to it.
-- Martin Luther King, Jr.
----- Original Message -----
From: Jeff Hayward <[EMAIL PROTECTED]>
To: <[EMAIL PROTECTED]>
Sent: Wednesday, April 28, 1999 2:08 PM
Subject: Re: failover for an NFS mounted maildir spool?
> On Wed, 28 Apr 1999, Racer X wrote:
>
> What I think is happening: qmail-local attempts to change to the root
path,
> and the chdir for THAT fails because the NFS mount is down. Around
line 90
> in qmail-local.c:
>
> if (chdir(dir) == -1) { if (error_temp(errno)) _exit(1); _exit(2); }
>
> Now according to the documentation, temporary failures are supposed to
have
> an exit code of 111, but for the moment I'll assume the "error_temp"
stuff
> is working as it's supposed to. The problem then becomes, why is
> qmail-local apparently interpreting the error (NFS read timeout?) as
> permanent and not temporary?
>
> No, that's the code in maildir_child, which is exiting a subprocess
> of the delivering qmail-local. It would probably be helpful to set
> up a test bed to replicate the problem and do a system call trace of
> qmail-lspawn and children to see what's actually going on.
>
> If it really is bouncing immediately on NFS failure it shouldn't be.
> It doesn't here.
>
> -- Jeff Hayward
>
>
>
>
