[Dovecot] Fresh Dovecot Install
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).
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
Yep - I did a source install *after* installing the Fedora Core 2 version (.99something) via yum.
You may have better luck doing that if you can find an RPM for dovecot for RH9 - then all you'll need to do is make a symlink from /usr/sbin/dovecot (move aside the RPM version first) to /usr/local/sbin/dovecot (your built-from-source version) after you make install dovecot from source, and the service scripts for the Redhat dovecot build will (probably) work.
On Tue, 2005-04-26 at 12:34, Jakob Curdes wrote:
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
Or, just edit the /etc/init.d script to call dovecot in /usr/local/sbin/....save making the symlink....
John Schettino wrote:
Yep - I did a source install *after* installing the Fedora Core 2 version (.99something) via yum.
You may have better luck doing that if you can find an RPM for dovecot for RH9 - then all you'll need to do is make a symlink from /usr/sbin/dovecot (move aside the RPM version first) to /usr/local/sbin/dovecot (your built-from-source version) after you make install dovecot from source, and the service scripts for the Redhat dovecot build will (probably) work.
On Tue, 2005-04-26 at 12:34, Jakob Curdes wrote:
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
I tried that, didn't work for me and I was too lazy to figure out why - the symlink worked however. On Tue, 2005-04-26 at 12:53, Robert Cooper wrote:
Or, just edit the /etc/init.d script to call dovecot in /usr/local/sbin/....save making the symlink....
John Schettino wrote:
Yep - I did a source install *after* installing the Fedora Core 2 version (.99something) via yum.
You may have better luck doing that if you can find an RPM for dovecot for RH9 - then all you'll need to do is make a symlink from /usr/sbin/dovecot (move aside the RPM version first) to /usr/local/sbin/dovecot (your built-from-source version) after you make install dovecot from source, and the service scripts for the Redhat dovecot build will (probably) work.
On Tue, 2005-04-26 at 12:34, Jakob Curdes wrote:
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
At this point in my linux knowledge I need to stick to the RPM's. I did find a dovecot rpm, downloaded it, and installed it on another RH9 machine. I need to figure out how now to remove the files on the other RH9 box that I started an install from source.
Thank you for the assistance.
George
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
machine. I need to figure out how now to remove the files on the other RH9 box that I started an install from source.
That depends on how you configured the make process. If you just said ./configure , you will finde EVERYTHING under /usr/local, that is, the dovecot binaries are under /usr/local/sbin, thew config file unter /usr/local/etc, the login helpers under /usr/local/libexec. If you specified a prefix like ./configure --prefix=/usr, then you will find everything under /usr.
Hope this helps, Jakob Curdes
Thanks for the tip. To make sure I ran a:
find / -name "*dovecot*"
which found the files in the directories you mentioned, which I then deleted.
Off to run the RPM version now.
On 4/28/05, Jakob Curdes jc@info-systems.de wrote:
machine. I need to figure out how now to remove the files on the other RH9 box that I started an install from source.
That depends on how you configured the make process. If you just said ./configure , you will finde EVERYTHING under /usr/local, that is, the dovecot binaries are under /usr/local/sbin, thew config file unter /usr/local/etc, the login helpers under /usr/local/libexec. If you specified a prefix like ./configure --prefix=/usr, then you will find everything under /usr.
Hope this helps, Jakob Curdes
participants (5)
-
GPL
-
Jakob Curdes
-
John Schettino
-
Robert Cooper
-
Timo Sirainen