On Thu, 10 Feb 2000, Ian Southam wrote:
> On Thu, Feb 10, 2000 at 11:12:26AM -0000 sysadmin wrote :
>
> > Would it seem sensible therfore that as a general rule anyone wanting to do
> > lookups (NIS, LDAP or other, etc.) for variables like "local_domains" should
> > really generate a cdb file from their master database periodically and
> > atomically move the new cdb to replace the existing cdb?
>
am in fear of managing things on my place with scripts.
on another topic (i build an radiusbackup with a script), a small error
accured and the backup-radius made an emty database.
if this happens to a mailserver tons of mails are bounced...
the database lookups works well on my place and i _NEED_ the flexibility
of the database.
IMHO, if you build cdb from a database you do not really need a databes!
what is the reason - when "local_domains" fails - that the mails are
_NOT_ placed in the queue waiting there til the database is able to answer
queries?
> Absolutely. As another poster said earlier it has huge advantages in terms of
> your system's resilience to parts of it being down.
>
> This method means that is your LDAP or SQL is down you mail keeps flowing,
> sure you probably cannot bring new accounts online but at least you are not
> flat on your face.
>
you can define backup databases as well.
> Centralised solutions look good on paper with one database feeding all the
> information out for the whole enterprise, the downside is that, if that
> central database isn't there neither is anything else.
>
robert
---
di. robert rotman inode.graz
phone -> ++43-(0)316 811451 ++43-(0)316 811451 <- fax
rotman@??? http://www.graz.inode.at/
--
this letter was written on recycled bytes used by deleted mail.
