Re: [Dovecot] How Can I Tell How Dovecot Was Installed?
Thanks Kenneth
On Tue, Aug 19, 2008 at 10:02 PM, Kenneth Porter shiva@sewingwitch.com 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.5....T 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
--On Wednesday, August 20, 2008 7:35 AM -0400 Blake Carver lists@lisnews.com 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.5....T 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.
on 8-20-2008 2:47 PM Kenneth Porter spake the following:
--On Wednesday, August 20, 2008 7:35 AM -0400 Blake Carver lists@lisnews.com 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.5....T 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!!!!
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
participants (4)
-
Blake Carver
-
Kenneth Porter
-
mouss
-
Scott Silva