Carlos E. R. wrote:
On 2014-04-03 16:01, James Knott wrote:
Anton Aylward wrote:
But that new drive died and I've just been though a install rather than an upgrade and there was no conflict between dovecot 2.1 and apparmor. I just tried changing Apparmor to enforce rather than complain with Dovecot. It still causes it to fail. Setting it back to complain restored Dovecot. Did you try aa-logprof yet?
Complain will fill your logs.
I get this response: Reading log entries from /var/log/messages. Updating AppArmor profiles in /etc/apparmor.d. Profile: /usr/sbin/dovecot Execute: /usr/bin/doveconf Severity: unknown (I)nherit / (P)rofile / (C)hild / (N)ame / (U)nconfined / (X)ix / (D)eny / Abo(r)t / (F)inish This conflicts with the man page: (A)llow, (D)eny, (N)ew, (G)lob last piece, (Q)uit So, what am I supposed to do? Why should this even be necessary? -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org