If you're only running 'makeuserdb' on host A, then there's not much of a problem with the current system. You can symlink userdb/whatever to the files you need, and run 'makeuserdb' on host A. Hosts B and C only need to read userdb.dat, so there shouldn't be a need for external files.
If you wanted (at any point) to maintain different userdb's on different hosts, while sharing the courier installation, you'd want to make the userdb directory and the userdb.dat file symlinks to /etc/local-courier/userdb (or something similar), so that each machine could maintain its own. It would not be sufficient to patch 'makeuserdb' in this case, because the hosts would overwrite the NFS mounted userdb.dat, and break the other hosts. On Thu, 2002-07-18 at 12:34, Ben Rosengart wrote: > > 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. ------------------------------------------------------- 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
