All of lore.kernel.org
 help / color / mirror / Atom feed
From: Peter Kjellerstedt <peter.kjellerstedt@axis.com>
To: openembedded-core@lists.openembedded.org
Subject: [PATCH 0/1] Disable syslog for all shadow commands supported by useradd_base.bbclass
Date: Thu, 14 Apr 2016 13:36:38 +0200	[thread overview]
Message-ID: <cover.1460633745.git.pkj@axis.com> (raw)

With the introduction of using userdel and groupdel when cleaning up a
recipe, I started getting messages in my system logs about the removal
of users and groups I know only exist in my recipes. It turned out
that the use of syslog had been disabled for useradd and groupadd when
building shadow-native, but never for the other commands supported by
useradd_base.bbclass. This commit rectifies this.

//Peter

The following changes since commit aab3c8d56dd6344b1e6cf38e610970bc68b2f624:

  linux-yocto: make aufs4 optional (2016-04-14 10:58:34 +0100)

are available in the git repository at:

  git://git.yoctoproject.org/poky-contrib pkj/shadow_disable_syslog
  http://git.yoctoproject.org/cgit.cgi/poky-contrib/log/?h=pkj/shadow_disable_syslog

Peter Kjellerstedt (1):
  shadow: Disable syslog for more commands

 .../0001-Disable-use-of-syslog-for-sysroot.patch   | 124 +++++++++++++++++++++
 .../shadow/files/disable-syslog.patch              |  34 ------
 meta/recipes-extended/shadow/shadow.inc            |   4 +-
 3 files changed, 126 insertions(+), 36 deletions(-)
 create mode 100644 meta/recipes-extended/shadow/files/0001-Disable-use-of-syslog-for-sysroot.patch
 delete mode 100644 meta/recipes-extended/shadow/files/disable-syslog.patch

-- 
2.1.0



             reply	other threads:[~2016-04-14 11:36 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-04-14 11:36 Peter Kjellerstedt [this message]
2016-04-14 11:36 ` [PATCH 1/1] shadow: Disable syslog for more commands Peter Kjellerstedt

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=cover.1460633745.git.pkj@axis.com \
    --to=peter.kjellerstedt@axis.com \
    --cc=openembedded-core@lists.openembedded.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.