cupsd locking up system during boot - targeted mode
Colin Walters
walters at redhat.com
Fri Aug 20 01:52:14 UTC 2004
On Thu, 2004-08-19 at 21:41 -0400, Jim Cornette wrote:
> I relabeled using the strict policy. I then changed the policy to
> targeted and rebooted.
You need to relabel after changing the policy type, not before.
> I believe I relabeled using targeted and permissive after the problem
> booting up.
That's the way to do it.
> When I pulled the avc messages from the latest /var/log/messages, it was
> about 180 kb large.
Eek :) If you booted in the targeted policy with a filesystem that was
labeled from a strict policy, a lot of those are probably going to just
be noise.
> I also had problems installing the latest rounds of updates. I had to
> setenforce 0 because of this error on line 142, using up2date . Here is
> an excerpt from the xterm..
>
> /etc/selinux/targeted/contexts/files/file_contexts: invalid context
> system_u:object_r:printer_device_t on line number 142
> /etc/selinux/targeted/contexts/files/file_contexts: invalid context
> system_u:object_r:printer_device_t on line number 142
This should be fixed now in rawhide (1.15.16-2).
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 189 bytes
Desc: This is a digitally signed message part
URL: <http://listman.redhat.com/archives/fedora-selinux-list/attachments/20040819/209b5fde/attachment.sig>
More information about the fedora-selinux-list
mailing list