>> Hmmm.../var should be labeled with system_u:object_r:var_t,
not file_t.
>> Need to relabel?
>
> I'm seeing these too. My /var is on a separate partition. Could this be
> the cause of the problem?
>
> Mar 31 20:04:18 random kernel: audit(1143831757.360:451): avc: denied { search }
for pid=1384 comm="pam_console_app" name="var" dev=hde3 ino=62785
scontext=system_u:system_r:pam_console_t:s0-s0:c0.c255
tcontext=system_u:object_r:file_t:s0 tclass=dir
> Mar 31 20:04:18 random kernel: EXT3 FS on hde3, internal journal
> Mar 31 20:04:18 random kernel: SELinux: initialized (dev tmpfs, type tmpfs), uses
transition SIDs
> Mar 31 20:04:18 random kernel: kjournald starting. Commit interval 5 seconds
> Mar 31 20:04:18 random kernel: EXT3 FS on hde8, internal journal
> Mar 31 20:04:18 random kernel: EXT3-fs: mounted filesystem with ordered data mode.
> Mar 31 20:04:18 random kernel: SELinux: initialized (dev hde8, type ext3), uses
xattr
What happens when you
restorecon -R -v /var
autorelabel works after /var mounted, but that error messages put before mount /var.
And /var on root partiotion still unlabeled. IMHO it is installer or filesystem package
bug.
--
Maxim Britov
GnuPG KeyID 0x4580A6D66F3DB1FB xmpp:maxim@modum.by icq 198171258
Fingerprint: 4059 B5C5 8985 5A47 8F5A 8623 4580 A6D6 6F3D B1FB
GnuPG-ru Team (
http://lists.gnupg.org/mailman/listinfo/gnupg-ru
xmpp:gnupg-ru@conference.jabber.ru)