Milter-greylist

On Fri, 15 Jun 2007, manu@... wrote:

> Dan Mahoney, System Admin <danm@...> wrote:
>
>> How is this different from how a crash is handled now?  We're at the mercy
>> of the berkeley engine instead of being at the mercy of the dumpfile.  If
>> the milter crashes while writing the dumpfile we're still screwed.
>
> You are not: we dump in a new file and rename the new file into the old
> one. That means that unless your OS plays the dangerous game of flushing
> metadata asynchronously, you are safe whatever happens. On reasonable
> systems, rename(2) says something like:
>
> "rename() guarantees that an instance of to will always exist, even if
> the system should crash in the middle of the operation."
>
> When I tried to add DBD support, I discovered I could not have such a
> garantee anymore, and this is why I gave it up.

So then the solution is simple.  Keep the same dumpfile we have now as an 
option.

-Dan

--

"It's three o'clock in the morning.  It's too late for 'oops'.  After
Locate Updates, don't even go there."

-Paul Baecker
  January 3, 2k
  Indeed, sometime after 3AM

--------Dan Mahoney--------
Techie,  Sysadmin,  WebGeek
Gushi on efnet/undernet IRC
ICQ: 13735144   AIM: LarpGM
Site:  http://www.gushi.org
---------------------------