Date: Tue, 31 Oct 1995 10:36:16 +0100 (MET) From: J Wunsch <j@uriah.heep.sax.de> To: ache@astral.msk.su (=?KOI8-R?Q?=E1=CE=C4=D2=C5=CA_=FE=C5=D2=CE=CF=D7?=) Cc: peter@jhome.dialix.com, CVS-commiters@freefall.freebsd.org, cvs-libexec@freefall.freebsd.org Subject: Re: cvs commit: src/libexec/mail.local Makefile mail.local.c Message-ID: <199510310936.KAA11541@uriah.heep.sax.de> In-Reply-To: <eBISUbmi04@ache.dialup.demos.ru> from "=?KOI8-R?Q?=E1=CE=C4=D2=C5=CA_=FE=C5=D2=CE=CF=D7?=" at Oct 31, 95 12:06:26 pm
next in thread | previous in thread | raw e-mail | index | archive | help
As =?KOI8-R?Q?=E1=CE=C4=D2=C5=CA_=FE=C5=D2=CE=CF=D7?= wrote: > > fsync in mail.local is evil probably only on UUCP sites when large > mail chunks parsed at once, on SMTP sites mail usually > arrives in async. order, so it not hits. Even though i'm as affected as you are (i get everything via UUCP), i wouldn't waste a nanosecond in thinking about _not_ fsynch'ing there. As well as i would not mount anything else than /tmp with the async option. -- cheers, J"org joerg_wunsch@uriah.heep.sax.de -- http://www.sax.de/~joerg/ -- NIC: JW11-RIPE Never trust an operating system you don't have sources for. ;-)
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?199510310936.KAA11541>