From: Daniel J Walsh <dwalsh@redhat.com>
To: LC Bruzenak <lenny@MagitekLtd.com>
Cc: SE Linux <selinux@tycho.nsa.gov>
Subject: Re: restorecon / matchpathcon
Date: Thu, 06 Nov 2008 11:59:00 -0500 [thread overview]
Message-ID: <49132254.2040600@redhat.com> (raw)
In-Reply-To: <1225989929.7321.39.camel@homeserver>
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
LC Bruzenak wrote:
> On Thu, 2008-11-06 at 11:35 -0500, Daniel J Walsh wrote:
>> -----BEGIN PGP SIGNED MESSAGE-----
>> Hash: SHA1
>>
>> LC Bruzenak wrote:
>>> I see no way to recursively/silently check path context.
>>>
>>> The matchpathcon command has a silent but no recursive option. It does
>>> return non-zero if something doesn't match.
>>>
>>> The restorecon command has both recursive and don't change options but
>>> no silent. It does not return non-zero if there is a change to be made,
>>> so a redirect of stdout to /dev/null wouldn't suffice.
>>>
>>> Is there another way/command?
>>>
>>> Thx,
>>> LCB.
>>>
>> find | xargs matchpathcon?
>
> I think in this case the $? return value would refer to the find not
> matchpathcon right?
>
> LCB.
>
matchpathcon -V PATH
Checks the context on disk versus the default, and sets the exit status
I believe.
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.9 (GNU/Linux)
Comment: Using GnuPG with Fedora - http://enigmail.mozdev.org
iEYEARECAAYFAkkTIlQACgkQrlYvE4MpobMqgQCfRK/l0bIFWcmCENRN5EAamm7K
TnoAoOvhSz4nTk6fLso9rGJypGs9g6mT
=4hGy
-----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-11-06 16:59 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-11-06 16:04 restorecon / matchpathcon LC Bruzenak
2008-11-06 16:35 ` Daniel J Walsh
2008-11-06 16:45 ` LC Bruzenak
2008-11-06 16:59 ` Daniel J Walsh [this message]
2008-11-06 17:19 ` LC Bruzenak
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=49132254.2040600@redhat.com \
--to=dwalsh@redhat.com \
--cc=lenny@MagitekLtd.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.