From: Bernd Petrovitsch <bernd@petrovitsch.priv.at>
To: noloader@gmail.com, kernelnewbies <kernelnewbies@kernelnewbies.org>
Subject: Re: SElinux and its own error code?
Date: Sun, 3 May 2020 16:02:05 +0000 [thread overview]
Message-ID: <5e692905-80db-fcf1-3141-fd54d3ea1c91@petrovitsch.priv.at> (raw)
In-Reply-To: <CAH8yC8kjRr29R8=zeUuyE5NKVDMZsdHMh+Z9a9mgP51VWYu-jQ@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 1009 bytes --]
Hi all!
On 03/05/2020 03:55, Jeffrey Walton wrote:
[...]
> I lost about four hours chasing inaccurate messages from Apache. It
Only 4hours? ;-) SCNR ...
> turns out SElinux was denying access, so the EPERM was not really
> accurate. But Apache saw EPERM or EACCESS and logged a message related
> to Posix permissions.
It's since day 1 so (and that day is quite sometime ago) - and we all
ran into that at one point.
Sry, I fear you will have to cope with it ...
In an ideal world, the Kernel emits errors via dmesg in such
situations (i.e. the selinux subsystem) - perhaps in some
way configurable (and I had my fair share of grep-ing through
countless lines of selinux error messages to find the really
relevant ones for one given application/process/situation/...).
MfG,
Bernd
PS: JftSoC: I find the errno's quite coarse too but it's the
way it is ....
--
There is no cloud, just other people computers.
-- https://static.fsf.org/nosvn/stickers/thereisnocloud.svg
[-- Attachment #2: pEpkey.asc --]
[-- Type: application/pgp-keys, Size: 2513 bytes --]
[-- Attachment #3: Type: text/plain, Size: 170 bytes --]
_______________________________________________
Kernelnewbies mailing list
Kernelnewbies@kernelnewbies.org
https://lists.kernelnewbies.org/mailman/listinfo/kernelnewbies
prev parent reply other threads:[~2020-05-03 16:03 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-05-03 3:55 SElinux and its own error code? Jeffrey Walton
2020-05-03 7:45 ` Greg KH
2020-05-03 7:50 ` Valdis Klētnieks
2020-05-03 7:59 ` Jeffrey Walton
2020-05-03 9:18 ` Greg KH
2020-05-03 16:02 ` Bernd Petrovitsch [this message]
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=5e692905-80db-fcf1-3141-fd54d3ea1c91@petrovitsch.priv.at \
--to=bernd@petrovitsch.priv.at \
--cc=kernelnewbies@kernelnewbies.org \
--cc=noloader@gmail.com \
/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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).