Full_Name: Chris Pepper Version: current website OS: irrelevant URL: http://www.OpenLDAP.org/faq/data/cache/192.html Submission from: (NULL) (216.112.226.150) slapd, by default, synchronizes the underlying DB after each modification. This is safe, but slow. In situations where you do not need this protection (such as on a slave server), you can disable write sync by specify the database configuration directive 'by specify the' should be 'by specifying the'. dbcacheNoWsync To make no write sync more safe, consider running a slave with write sync on. This slave then becomes a live backup for the master. 'write sync more safe,' should be 'write sync safer,'.
The FAQ is interactive. Feel free to make corrections yourself [enable editing commands via Appearances link]. At 02:52 PM 6/27/00 GMT, pepper@reppep.com wrote: >Full_Name: Chris Pepper >Version: current website >OS: irrelevant >URL: http://www.OpenLDAP.org/faq/data/cache/192.html >Submission from: (NULL) (216.112.226.150) > > >slapd, by default, synchronizes the underlying DB after each modification. This >is safe, but slow. In situations where you do not need this protection (such as >on a slave server), you can disable write sync by specify the database >configuration directive > 'by specify the' should be > 'by specifying the'. > >dbcacheNoWsync > > >To make no write sync more safe, consider running a slave with write sync on. >This slave then becomes a live backup for the master. > 'write sync more safe,' should be > 'write sync safer,'. > > >
At 6:17 PM -0700 2000/06/28, Kurt D. Zeilenga wrote: >The FAQ is interactive. Feel free to make corrections yourself >[enable editing commands via Appearances link]. Done, thanks. Chris Pepper >At 02:52 PM 6/27/00 GMT, pepper@reppep.com wrote: >>Full_Name: Chris Pepper >>Version: current website >>OS: irrelevant > >URL: http://www.OpenLDAP.org/faq/data/cache/192.html >>Submission from: (NULL) (216.112.226.150) >> >> > >slapd, by default, synchronizes the underlying DB after each >modification. This >>is safe, but slow. In situations where you do not need this >>protection (such as >>on a slave server), you can disable write sync by specify the database >>configuration directive >> 'by specify the' should be >> 'by specifying the'. >> >>dbcacheNoWsync >> >> >>To make no write sync more safe, consider running a slave with write sync on. >>This slave then becomes a live backup for the master. >> 'write sync more safe,' should be >> 'write sync safer,'. > > >> >> -- Chris Pepper | Shooting Gallery Interactive | New: <pepper@reppep.com>
moved from Incoming to Web
changed notes changed state Open to Closed
fixed by user