Well that didn't last long.
I was in a hurry and didn't realise that cyrus's demons hadn't started
and initialised databases in /var/imap
Now I'm officially stumped.
--John
John Huttley wrote:
Okaaayyy,
I've just been fiddling with my x86 system and suddenly it works.
The trouble is I don't know what it was that I did to fix it. I can only
hope it doesn't un-fix itself just as suddenly.
Regards,
JOhn
John Huttley wrote:
Hi Chris,
I've just compared with my X64 test system. Both run
2.6.20-hardened-r4 with xfs filesystems.
Both had the problems with the emerge of selinux-base-policy
segfaulting when trying to load the base policy.
Both fixed by using semodule manually.
Both have /var/imap with the correct context.
The X64 system works.
Clearly I'll have check it out in detail.
regards,
john
Chris PeBenito wrote:
On Wed, 2007-08-15 at 11:10 -0400, Chris PeBenito wrote:
On Wed, 2007-08-15 at 11:07 +1200, John Huttley wrote:
I've successfully made myself a pp file for cyrus and rlpkg labels
the
file correctly.
However when cyrus runs, it then creates some files itself, which are
not labeled.
What the standard practice for coping with this?
Something is broken. It should never be creating unlabeled files.
Which kernel and version do you have, and which filesystem is this on?
Actually, the only way it could legitimately be creating unlabeled files
is if the directory itself is unlabeled.
--
[EMAIL PROTECTED] mailing list
