On Wed, Jan 02, 2002 at 12:43:59AM +0000, Michael Carmack wrote: > On Tue, Jan 01, 2002 at 05:58:09PM -0500, Sam Varshavchik wrote: > > > > binary, but the system startup imapd script. So, something is seriously > > screwed up here. Unfortunately, it is not possible to determine what that > > "something" is. > > You've hit it! Yes, I compiled and installed this myself, and bin/imapd > IS a symlink to the imapd startup script. I've posted the complete build > log to: > > http://karmak.org/2002/01/courier/i686-pc-linux-gnu.1.log
Woo-hoo! IMAP is now working. The problem was that I don't typically use 'sbin' on my machine, instead consolidating all binaries into bin. I specify this at 'configure' time with --sbindir=/path/to/bin. In the case of Courier, as you've probably guessed by this point, there is file named 'imapd' in BOTH bin and sbin: The binary in bin, and the script in sbin. So, the installation did exactly what I told it to, first installing the binary in 'bindir', then promptly overwriting it with the script in 'sbindir'. I changed the configure variable, and now things are working like a charm. Many thanks for taking the time out to find the problem. As a token of thanks I'll be typing up a document describing the way I got Courier installed and running on my system. Thanks again, m. _______________________________________________ courier-users mailing list [EMAIL PROTECTED] Unsubscribe: https://lists.sourceforge.net/lists/listinfo/courier-users
