-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On Thursday, 2014-04-03 at 22:22 -0400, James Knott wrote: For some reason I don't know, I missed this post. Sorry.
Carlos E. R. wrote:
Run "rcrpmconfigcheck". Do you see any output related to apparmour or dovecot? /etc/apparmor.d/usr.lib.dovecot.deliver.rpmnew /etc/apparmor.d/usr.lib.dovecot.imap.rpmnew /etc/apparmor.d/usr.lib.dovecot.imap-login.rpmnew /etc/apparmor.d/usr.lib.dovecot.managesieve-login.rpmnew /etc/apparmor.d/usr.lib.dovecot.pop3.rpmnew /etc/apparmor.d/usr.lib.dovecot.pop3-login.rpmnew /etc/apparmor.d/usr.sbin.dovecot.rpmnew
If you do, that's your problem.
Why is it my problem when this is a fresh install just a couple of months ago? Shouldn't the distro be expected to work properly "out of the box"?
"This is your problem" it is not that I say that you caused this problem. I meant that this is the cause of your problem. Even if I'm fluent in English, it is not my first language, and some times maybe I do not express myself well enough. :-) So, your problem is that, even although there was an online update that should have corrected your problem with dovecot and AA, it was not /really/ applied. For instance, you had problems with the "/usr/sbin/dovecot" AA profile. But the update is in "/etc/apparmor.d/usr.sbin.dovecot.rpmnew", while the old and active file is "/etc/apparmor.d/usr.sbin.dovecot". You have to replace /etc/apparmor.d/usr.sbin.dovecot with /etc/apparmor.d/usr.sbin.dovecot.rpmnew, and do that for all the "*rpmnew" files in that list. This is your job as system administrator ;-) The script "rcrpmconfigcheck" runs on every boot, I think. When you boot in text mode you see it, but with modern graphical displays, you miss it. You can also look on the file "/var/adm/rpmconfigcheck". After any update you should have a look at the output of "rcrpmconfigcheck", and decide what to do. Typically I make a backup of the files, then open both with "meld", to compare the differences, keep what I want, and accept the new proposed changes in the update. As I say, it is your job as Linux system administrator, you have to earn your keep >:-) Now you'll ask: why were not the files replaced directly? Well, because maybe you did local changes to them that you want to keep. Although the rpm command is capable of finding out if the configuration files were changed, and if not, replace them directly. Why this happens some times, and not some other times, I don't know. - -- Cheers, Carlos E. R. (from 13.1 x86_64 "Bottle" at Telcontar) -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.22 (GNU/Linux) iEYEARECAAYFAlNB2Z4ACgkQtTMYHG2NR9Uy6ACfbRfrBNnlMHBEPf6SdsIUj8aO tYYAnjM8XpWcZiMuLnHPf+TpchrUXjNH =Kfzh -----END PGP SIGNATURE----- -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org