On Thu, Jul 18, 2002 at 02:30:24PM -0400, Sam Varshavchik wrote: > > Why don't you simply build Courier using --sysconfdir=/etc/courier and > --with-userdb=/etc/courier/userdb, and install a soft link on each host, > /etc/courier, that points to the right configuration directory for that > host where all the configuration files, not just userdb, are saved. > > I.E., on host A /etc/courier points to /foo/export, on host B /etc/courier > points someplace else. You now have a consistent naming schere and you > don't have to remember where on each host this directory may be found -- > you just look where /etc/courier points to.
Let's run over this once more. Hosts B and C run courier. They use different userdbs. Each mounts a filesystem from host A as /courier. So, in B's fstab, you see something more or less like: A:/export/B /courier nfs rw 0,0 Host A does not run courier. It's a configuration management host. It stores the userdb source files somewhere, and writes B's userdb data files to /export/B, and C's to /export/C. I think I realized where the confusion stems from. You think I'm running makeuserdb on hosts B and C. If I did that, then there would not be a problem. But I have been proceeding all this time on the assumption that makeuserdb would be running on host A. The problem with running makeuserdb on hosts B and C is that it costs me an ssh every time I change a database on host A. On the other hand, the locking of the database is more likely to work correctly. I have to think about this more. -- Ben Rosengart (212) 741-4400 x215 Microsoft has argued that open source is bad for business, but you have to ask, "Whose business? Theirs, or yours?" --Tim O'Reilly ------------------------------------------------------- This sf.net email is sponsored by:ThinkGeek Welcome to geek heaven. http://thinkgeek.com/sf _______________________________________________ courier-users mailing list [EMAIL PROTECTED] Unsubscribe: https://lists.sourceforge.net/lists/listinfo/courier-users
