From: bugzilla@busybox.net
To: buildroot@uclibc.org
Subject: [Buildroot] [Bug 15496] New: auditd startup broken when coreutils is installed
Date: Wed, 29 Mar 2023 13:56:33 +0000 [thread overview]
Message-ID: <bug-15496-163@https.bugs.busybox.net/> (raw)
https://bugs.busybox.net/show_bug.cgi?id=15496
Bug ID: 15496
Summary: auditd startup broken when coreutils is installed
Product: buildroot
Version: 2023.02
Hardware: All
OS: Linux
Status: NEW
Severity: minor
Priority: P5
Component: Other
Assignee: unassigned@buildroot.uclibc.org
Reporter: jbittner.br.bugs@gmail.com
CC: buildroot@uclibc.org
Target Milestone: ---
In the launch script /etc/init.d/S02auditd (buildroot/package/audit/S02auditd),
line 23: mkdir -p /var/log/audit -Z `selabel_lookup -b file -k
/var/log/audit | cut -d ' ' -f 3`
does not work when coreutils mkdir replaces the one supplied by busybox. The
-Z context needs to be placed before the directory name with coreutils and
BusyBox will accept it both ways.
With coreutils, a folder is created with the name of the context in the current
directory, auditd appears to start, appears in ps, but does no SELinux logging.
Doing a restart will show an OK on stopping and a FAIL on starting. Starting
again shows an OK but no logging occurs.
--
You are receiving this mail because:
You are on the CC list for the bug.
_______________________________________________
buildroot mailing list
buildroot@buildroot.org
https://lists.buildroot.org/mailman/listinfo/buildroot
next reply other threads:[~2023-03-29 13:56 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-03-29 13:56 bugzilla [this message]
2024-06-15 15:07 ` [Buildroot] [Bug 15496] auditd startup broken when coreutils is installed bugzilla
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=bug-15496-163@https.bugs.busybox.net/ \
--to=bugzilla@busybox.net \
--cc=buildroot@uclibc.org \
/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.