Kelly, Terence P wrote:
For a variety of reasons I would like to run the back-end database beneath slapd on a different machine than slapd.
This appears to be difficult using the Berkeley DB.
Makes no sense at all, given that BerkeleyDB is an *embedded* database. I.e., it doesn't run in a separate process, it is designed to run in the same process as the application that uses it.
Can anyone offer suggestions on how to run slapd and the database --- any database --- on separate machines?
Why? I think if you provide more details about your motivation it would be easier to suggest usable alternatives.