Re: [Dovecot] How Can I Tell How Dovecot Was Installed?
on 8-20-2008 2:47 PM Kenneth Porter spake the following: --On Wednesday, August 20, 2008 7:35 AM -0400 Blake Carver [EMAIL PROTECTED] wrote: I guess I'm not quite sure how to interpret this to help me figure out my problem, there are changes rpm reports, does this mean that an RPM was installed but so was a source package? rpm -V -v dovecot c /etc/dovecot.conf This is a config file, as denoted by the c. The row of dots means the file is pristine (hasn't been modified since it was installed). S.5T c /etc/rc.d/init.d/dovecot This config file is different from the package. I don't recall what all the flags mean but the 5 means an MD5 checksum mismatch. As a rule, initscripts shouldn't be modified unless you're doing something tricky, so this was likely replaced from a tarball install. prelink: /usr/libexec/dovecot/dict: at least one of file's dependencies has changed since prelinking S.?. /usr/libexec/dovecot/dict prelink: /usr/libexec/dovecot/dovecot-auth: at least one of file's dependencies has changed since prelinking S.?. /usr/libexec/dovecot/dovecot-auth All of these prelink errors suggest that your binaries were overwritten from a tarball installation. The easy fix is to erase (rpm -e) the package and re-install it, likely upgrading to a newer package at the same time. But a rpm install will not overwrite the tarball install since tarball installs usually go to /usr/local or under /opt while rpm installs will go into /usr directly. I don't know if the tarball has a make uninstall command, but the previous admin should have left the unpacked source around from the install somewhere in either /root or in his home directory. That can give more clues. d /usr/share/doc/dovecot-1.0/REDHAT-FAQ.txt d files are documentation, and if you're tight on disk space, you can suppress installation of documentation when the package is installed. -- MailScanner is like deodorant... You hope everybody uses it, and you notice quickly if they don't signature.asc Description: OpenPGP digital signature
Re: [Dovecot] How Can I Tell How Dovecot Was Installed?
Scott Silva wrote: on 8-20-2008 2:47 PM Kenneth Porter spake the following: All of these prelink errors suggest that your binaries were overwritten from a tarball installation. The easy fix is to erase (rpm -e) the package and re-install it, likely upgrading to a newer package at the same time. But a rpm install will not overwrite the tarball install since tarball installs usually go to /usr/local or under /opt while rpm installs will go into /usr directly. sure, but - if you intend to always build from sources, you don't really care about packages. it's only once you get a problem that you start becoming more careful. - however you do it, init scripts generally go under /etc (at least under Linux). I don't know if the tarball has a make uninstall This almost never exists. it is not easy to implement (because you don't want to remove files installed otherwise) without implementing a package manager. an install.log would be nice though... command, but the previous admin should have left the unpacked source around from the install somewhere in either /root or in his home directory. That can give more clues. well, he could should, but he generally would never :-) OP can try to find the distribution that was installed from source and use it to determine which files it installs, or he could ignore it and only remove the files that create problems with a new version. if he is motivated enough, reinstalling the whole system may be worth the pain. d /usr/share/doc/dovecot-1.0/REDHAT-FAQ.txt d files are documentation, and if you're tight on disk space, you can suppress installation of documentation when the package is installed. or buy more disk ;-p
Re: [Dovecot] How Can I Tell How Dovecot Was Installed?
Thanks Kenneth On Tue, Aug 19, 2008 at 10:02 PM, Kenneth Porter [EMAIL PROTECTED] wrote: The best you can do here is to query the database to see if the files it knows about match those on the disk. For that, use rpm -V -v dovecot. That does a verbose verify and tells you what files it knows about have been changed in some way. I guess I'm not quite sure how to interpret this to help me figure out my problem, there are changes rpm reports, does this mean that an RPM was installed but so was a source package? rpm -V -v dovecot c /etc/dovecot.conf c /etc/pam.d/dovecot c /etc/pki/dovecot/dovecot-openssl.cnf S.5T c /etc/rc.d/init.d/dovecot /usr/lib/dovecot /usr/lib/dovecot/imap /usr/lib/dovecot/imap/lib01_acl_plugin.so /usr/lib/dovecot/imap/lib01_convert_plugin.so /usr/lib/dovecot/imap/lib01_quota_plugin.so /usr/lib/dovecot/imap/lib01_zlib_plugin.a /usr/lib/dovecot/imap/lib01_zlib_plugin.la /usr/lib/dovecot/imap/lib01_zlib_plugin.so /usr/lib/dovecot/imap/lib02_imap_quota_plugin.a /usr/lib/dovecot/imap/lib02_imap_quota_plugin.la /usr/lib/dovecot/imap/lib02_imap_quota_plugin.so /usr/lib/dovecot/imap/lib02_trash_plugin.so /usr/lib/dovecot/lda /usr/lib/dovecot/lda/lib01_acl_plugin.so /usr/lib/dovecot/lda/lib01_convert_plugin.so /usr/lib/dovecot/lda/lib01_quota_plugin.so /usr/lib/dovecot/lda/lib02_trash_plugin.so /usr/lib/dovecot/lib01_acl_plugin.a /usr/lib/dovecot/lib01_acl_plugin.la /usr/lib/dovecot/lib01_acl_plugin.so /usr/lib/dovecot/lib01_convert_plugin.a /usr/lib/dovecot/lib01_convert_plugin.la /usr/lib/dovecot/lib01_convert_plugin.so /usr/lib/dovecot/lib01_quota_plugin.a /usr/lib/dovecot/lib01_quota_plugin.la /usr/lib/dovecot/lib01_quota_plugin.so /usr/lib/dovecot/lib02_trash_plugin.a /usr/lib/dovecot/lib02_trash_plugin.la /usr/lib/dovecot/lib02_trash_plugin.so /usr/lib/dovecot/pop3 /usr/lib/dovecot/pop3/lib01_convert_plugin.so /usr/lib/dovecot/pop3/lib01_quota_plugin.so /usr/libexec/dovecot /usr/libexec/dovecot/checkpassword-reply /usr/libexec/dovecot/deliver prelink: /usr/libexec/dovecot/dict: at least one of file's dependencies has changed since prelinking S.?. /usr/libexec/dovecot/dict prelink: /usr/libexec/dovecot/dovecot-auth: at least one of file's dependencies has changed since prelinking S.?. /usr/libexec/dovecot/dovecot-auth /usr/libexec/dovecot/gdbhelper /usr/libexec/dovecot/imap prelink: /usr/libexec/dovecot/imap-login: at least one of file's dependencies has changed since prelinking S.?. /usr/libexec/dovecot/imap-login /usr/libexec/dovecot/pop3 prelink: /usr/libexec/dovecot/pop3-login: at least one of file's dependencies has changed since prelinking S.?. /usr/libexec/dovecot/pop3-login /usr/libexec/dovecot/rawlog prelink: /usr/libexec/dovecot/ssl-build-param: at least one of file's dependencies has changed since prelinking S.?. /usr/libexec/dovecot/ssl-build-param /usr/sbin/dovecot prelink: /usr/sbin/dovecotpw: at least one of file's dependencies has changed since prelinking S.?. /usr/sbin/dovecotpw /usr/share/doc/dovecot-1.0 d /usr/share/doc/dovecot-1.0/REDHAT-FAQ.txt d /usr/share/doc/dovecot-1.0/USE-WIKI-INSTEAD /usr/share/doc/dovecot-1.0/UW-to-Dovecot-Migration d /usr/share/doc/dovecot-1.0/UW-to-Dovecot-Migration/maildir-migration.txt d /usr/share/doc/dovecot-1.0/UW-to-Dovecot-Migration/migrate-folders d /usr/share/doc/dovecot-1.0/UW-to-Dovecot-Migration/migrate-users d /usr/share/doc/dovecot-1.0/UW-to-Dovecot-Migration/perfect_maildir.pl d /usr/share/doc/dovecot-1.0/auth-protocol.txt d /usr/share/doc/dovecot-1.0/auth.txt d /usr/share/doc/dovecot-1.0/configuration.txt d /usr/share/doc/dovecot-1.0/design.txt /usr/share/doc/dovecot-1.0/examples d /usr/share/doc/dovecot-1.0/examples/dovecot-ldap.conf d /usr/share/doc/dovecot-1.0/examples/dovecot-sql.conf d /usr/share/doc/dovecot-1.0/examples/mkcert.sh d /usr/share/doc/dovecot-1.0/index.txt d /usr/share/doc/dovecot-1.0/mail-storages.txt d /usr/share/doc/dovecot-1.0/multiaccess.txt d /usr/share/doc/dovecot-1.0/nfs.txt d /usr/share/doc/dovecot-1.0/securecoding.txt d /usr/share/doc/dovecot-1.0/variables.txt /var/lib/dovecot /var/run/dovecot /var/run/dovecot/login
Re: [Dovecot] How Can I Tell How Dovecot Was Installed?
Blake Carver wrote: Thanks Rod, So I guess my big question here is, how do I upgrade this sucker? I'd love to just use an RPM, but if this was originally installed via source will I mess it up? When I do rpm -qa | grep dovecot I get dovecot-1.0-1.2.rc15.el5 I think the default for RHEL 5. CentOS 5, etc. BUT dovecot --version shows me a different # Meaning your are not running the RPM installed version. On Tue, Aug 19, 2008 at 5:15 PM, Roderick A. Anderson [EMAIL PROTECTED] wrote: Unless, like he said above it may have been installed via a tarball. dovecot --version You should and see if there is more than one installed and So --version shows just one version, 1.0.3 (pretty damn old) So try a 'which dovecot' to see if you have more than one installed. And if there is more than one look in /etc/init.d (for SysV-type systems - YMMV) for a dovecot file and see which one it is calling. 'which dovecot' just gives me /usr/local/sbin/dovecot Taking a look at /etc/init.d/dovecot shows me it's staring Dovecot using /usr/local/sbin/dovecot My guess (without know what dovecot --version reported) would be that you are probably running a tarball installed version. A quick check of the repositories, including rpmforge, indicates the latest official distribution version is 1.0.7-2.el5. To get the latest and greatest you'll have to either build your own RPM or do a tarball install. Good computing, Rod -- and ps auxw | grep dovecot does show that's the one that's running /usr/local/sbin/dovecot
Re: [Dovecot] How Can I Tell How Dovecot Was Installed?
On 8/20/2008, Roderick A. Anderson ([EMAIL PROTECTED]) wrote: To get the latest and greatest you'll have to either build your own RPM or do a tarball install. Or just use atrpms.net... Why anyone would knowingly run ancient versions of critical apps is beyond me. -- Best regards, Charles
Re: [Dovecot] How Can I Tell How Dovecot Was Installed?
Because it isn't busted? Charles Marcus wrote: Why anyone would knowingly run ancient versions of critical apps is beyond me. -- Stewart Dean, Unix System Admin, Henderson Computer Resources Center of Bard College, Annandale-on-Hudson, New York 12504 [EMAIL PROTECTED] voice: 845-758-7475, fax: 845-758-7035
Re: [Dovecot] How Can I Tell How Dovecot Was Installed?
On 8/20/2008 11:35 AM, Stewart Dean wrote: Because it isn't busted? Just because you don't *think* its busted doesn't mean its not... Of course, I'm not saying that running an up to date version completely solves this question - *all* s/w has bugs, its just a matter of when they are discovered - but I'd rather be running a version that has fixes for *known* bugs/issues - not to mention the performance improvements, new features, etc. But of course, thats the nice thing about free software... we're all free to do it our way... :) -- Best regards, Charles
Re: [Dovecot] How Can I Tell How Dovecot Was Installed?
Blake Carver wrote: Thanks Rod, So I guess my big question here is, how do I upgrade this sucker? I'd love to just use an RPM, but if this was originally installed via source will I mess it up? When I do rpm -qa | grep dovecot I get dovecot-1.0-1.2.rc15.el5 BUT dovecot --version shows me a different # On Tue, Aug 19, 2008 at 5:15 PM, Roderick A. Anderson [EMAIL PROTECTED] wrote: Unless, like he said above it may have been installed via a tarball. dovecot --version You should and see if there is more than one installed and So --version shows just one version, 1.0.3 (pretty damn old) So try a 'which dovecot' to see if you have more than one installed. And if there is more than one look in /etc/init.d (for SysV-type systems - YMMV) for a dovecot file and see which one it is calling. 'which dovecot' just gives me /usr/local/sbin/dovecot Taking a look at /etc/init.d/dovecot shows me it's staring Dovecot using /usr/local/sbin/dovecot and ps auxw | grep dovecot does show that's the one that's running /usr/local/sbin/dovecot so you're somewhat lucky: the software was installed (probably from source) in a well known place (/usr/local). you can remove this by looking at all dovecot and postfix files under /usr/local/. you can do the same for other software. yum and rpm don't install software in /usr/local/. you'll have to remove startup scripts as well. once you've removed all the old stuff, you can install new packages (if you have a development env somewhere, you can build recent SRPMs instead of using the old available ones).
Re: [Dovecot] How Can I Tell How Dovecot Was Installed?
--On Wednesday, August 20, 2008 11:23 AM -0400 Charles Marcus [EMAIL PROTECTED] wrote: Why anyone would knowingly run ancient versions of critical apps is beyond me. Stability. It's not uncommon for apps to be interdependent. Upgrading one can have unexpected consequences in another app. For this reason, RHEL back-ports fixes for critical apps rather that automatically upgrading to the latest version. For it to do so, it needs to have patches for specific issues registered in Bugzilla. For those of us willing to take the risk of wholesale upgrade to the bleeding edge, we can grab an RPM from Red Hat's Rawhide distro. My practice is usually to grab the source RPM and rebuild it to match the libraries I have on my distro (CentOS 5). In some cases, 3rd party distros like atrpms.net and RPMForge carry the latest version pre-built for many distros. If I need a package that RPMForge supports, I'll grab the binary from there.
Re: [Dovecot] How Can I Tell How Dovecot Was Installed?
--On Wednesday, August 20, 2008 7:35 AM -0400 Blake Carver [EMAIL PROTECTED] wrote: I guess I'm not quite sure how to interpret this to help me figure out my problem, there are changes rpm reports, does this mean that an RPM was installed but so was a source package? rpm -V -v dovecot c /etc/dovecot.conf This is a config file, as denoted by the c. The row of dots means the file is pristine (hasn't been modified since it was installed). S.5T c /etc/rc.d/init.d/dovecot This config file is different from the package. I don't recall what all the flags mean but the 5 means an MD5 checksum mismatch. As a rule, initscripts shouldn't be modified unless you're doing something tricky, so this was likely replaced from a tarball install. prelink: /usr/libexec/dovecot/dict: at least one of file's dependencies has changed since prelinking S.?. /usr/libexec/dovecot/dict prelink: /usr/libexec/dovecot/dovecot-auth: at least one of file's dependencies has changed since prelinking S.?. /usr/libexec/dovecot/dovecot-auth All of these prelink errors suggest that your binaries were overwritten from a tarball installation. The easy fix is to erase (rpm -e) the package and re-install it, likely upgrading to a newer package at the same time. d /usr/share/doc/dovecot-1.0/REDHAT-FAQ.txt d files are documentation, and if you're tight on disk space, you can suppress installation of documentation when the package is installed.
Re: [Dovecot] How Can I Tell How Dovecot Was Installed?
Blake Carver wrote: I'm trying to help someone with Dovecot, and it looks like this one is a few versions behind. They say that they're not sure if it was installed Via an RPM or a source tarball. Dovecot is use MySQL. This is a RHEL5 server. There are RPMs listed as installed (rpm -qa) but I don't know how I can tell what was used to install the currently used set up. (also asking on the Postifix list) Is there something in a conf file or something that shows me how it was installed? same method as for postfix :) more generally, # rpm -qa lists all the installed packages see the rpm man page for more options/functionalities (you can check which package owns a file, and you can get the list of files installed by a pckage, ... etc).
