From: Daniel J Walsh <dwalsh@redhat.com>
To: anebi@iguanait.com
Cc: selinux@tycho.nsa.gov
Subject: Re: Problem with multisame specification warning messages RHEL 5
Date: Tue, 27 May 2008 08:15:50 -0400 [thread overview]
Message-ID: <483BFB76.2050306@redhat.com> (raw)
In-Reply-To: <1211791497.5210.21.camel@hugo.iguanait.com>
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
Ali Nebi wrote:
| Hi,
|
| we have installed RHEL 5 and after update we get these warnings:
|
| /etc/selinux/targeted/contexts/files/file_contexts: Multiple same
| specifications for /usr/local/lost\+found/.*.
| /etc/selinux/targeted/contexts/files/file_contexts: Multiple same
| specifications for /usr/local/\.journal.
| /etc/selinux/targeted/contexts/files/file_contexts: Multiple same
| specifications for /usr/local/lost\+found.
|
| I tried to remove these with semanage tool this way:
|
| semanage fcontext -d "/usr/local/lost\+found/.*"
|
| /usr/sbin/semanage: File context for /usr/local/lost\+found/.* is
| defined in policy, cannot be deleted
|
| I got the error above, that i can't delete this policy, because it is
| defined in policy. How can i fix this problem? If i edit manually user
| definitions file, will it be generated automatically after restart and i
| will get the same warnings?
|
| There is already a bug report in centos bugzilla. But i would like to
| find out how to fix this problem.
|
| Please help me for this.
|
| Thanks in advanced!
|
|
| --
| This message was distributed to subscribers of the selinux mailing list.
| If you no longer wish to subscribe, send mail to
majordomo@tycho.nsa.gov with
| the words "unsubscribe selinux" without quotes as the message.
This usually means the system thinks you have a user account home
directory in /usr/local, If there is a system account in /usr/local
make sure its shell is /sbin/nologin or /bin/false and then run semodule -B
To regenerate the home directory file context.
If you have real users with the home directory in /usr/local, you need
to move them in order for SELinux to get the file labelling correct.
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.9 (GNU/Linux)
Comment: Using GnuPG with Fedora - http://enigmail.mozdev.org
iEYEARECAAYFAkg7+3UACgkQrlYvE4MpobO1kwCfR1a+RaI0l5bTqvqwiKx/OHqA
AoQAoM0RJN5atVpEseTgnHzxkXRCuZCj
=30dH
-----END PGP SIGNATURE-----
--
This message was distributed to subscribers of the selinux mailing list.
If you no longer wish to subscribe, send mail to majordomo@tycho.nsa.gov with
the words "unsubscribe selinux" without quotes as the message.
next prev parent reply other threads:[~2008-05-27 12:17 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-05-26 8:44 Problem with multisame specification warning messages RHEL 5 Ali Nebi
2008-05-27 12:15 ` Daniel J Walsh [this message]
2008-05-27 20:47 ` Ali Nebi
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=483BFB76.2050306@redhat.com \
--to=dwalsh@redhat.com \
--cc=anebi@iguanait.com \
--cc=selinux@tycho.nsa.gov \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.