Working on an RH9 box. Did not use yum. Downloaded the "dovecot-stable-latest.tar.gz". Uncompressed it, downloaded and installed gcc. Ran the following: ./configure make sudo make install Seemed to have done its thing. I'll admit I am not well versed in using "make" or compiling anything. When I install I usually use yum on fedora machines. This one being an RH9 machine I have plugged yum into the fedora legacy project and it did not let me install dovecot via yum. So I opted for this route. Regardless, if I run 'which dovecot' I see "/usr/local/sbin/dovecot" However now I do not seem to be able to see it run. I get nothing when I: rpm -qa | grep dovecot ps aux | grep dovecot service dovecot status SO AM HAVE MISSED SOMETHING! Is there another script I need to run? Suggestions welcome. Thanks, George
On Tue, 2005-04-26 at 15:08 -0400, GPL wrote:> Regardless, if I run 'which dovecot' I see "/usr/local/sbin/dovecot" > However now I do not seem to be able to see it run.You'll most likely have to modify /usr/local/etc/dovecot.conf. The error message should be in /var/log/mail.log (or something similar). -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 189 bytes Desc: This is a digitally signed message part URL: <http://dovecot.org/pipermail/dovecot/attachments/20050426/81bb5767/attachment-0001.bin>
>I get nothing when I: > >rpm -qa | grep dovecot >ps aux | grep dovecot >service dovecot status > > >I suppose you are expecting that after doing a "make install", the application already runs, like you are used from rpm installs ? That will not be the case. I am not even sure if the dovecot install process places a start/stop script in /etc/init.d. Often you have to do many things on your own after a source install, like adapting or creating a start/stop script or copying and modifying a sample configuration file. That's what Mark pointed out : you should probably at least go through the provided configuration file and then you can try and start dovecot by hand and observer the relevant logfiles, depending on your dsitribution. If you find that all works well, you can use the start/stop mechanism to integrate dovecot startup into your system startup. Sorry, but when compiling source packages you have to "RTFM" and adapt the explanations to your configuration. If you configured dovecot and started it and it fails to run, start it from the command line and watch out for fatal errors on STDOUT or in the logs. Most probably the ports are in use by another pop/imap program. Hope this helps, Jakob Curdes