Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
To: buildroot@busybox.net
Subject: [Buildroot] Howto use "Makeusers"
Date: Fri, 4 Dec 2015 15:03:54 +0100	[thread overview]
Message-ID: <20151204150354.03453463@free-electrons.com> (raw)
In-Reply-To: <56619CCF.6040008@gmx.de>

Andreas,

On Fri, 4 Dec 2015 15:01:51 +0100, Andreas Ehmanns wrote:

> to make an openldap server available for buildroot I created an init 
> script which starts the ldap server as non-privileged user (and group).
> Since the ldap user and group is not existing on the target I searched 
> for a way to let the openldap package add the user and group to the 
> target filesystem. The buildroot documentation describes in chapter 23 
> the syntax of "makeusers". So far so good, but I have no idea to which 
> file I should add the corresponding makeusers command.
> 
> I grepped the buildroot tree for an example but unfortunately did not 
> found a package using this command.
> 
> Does anybody have an example how to do this.

Directly in your .mk file, using a variable named <pkg>_USERS. See
package/dbus/dbus.mk for an example:

define DBUS_USERS
        dbus -1 dbus -1 * /var/run/dbus - dbus DBus messagebus user
endef

This is also documented in the manual, which says:

   LIBFOO_USERS lists the users to create for this package, if it
   installs a program you want to run as a specific user (e.g. as a
   daemon, or as a cron-job). The syntax is similar in spirit to the
   makedevs one, and is described in the Chapter 23, Makeusers syntax
   documentation. This variable is optional.

Hope this helps,

Thomas
-- 
Thomas Petazzoni, CTO, Free Electrons
Embedded Linux, Kernel and Android engineering
http://free-electrons.com

  reply	other threads:[~2015-12-04 14:03 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-12-04 14:01 [Buildroot] Howto use "Makeusers" Andreas Ehmanns
2015-12-04 14:03 ` Thomas Petazzoni [this message]
2015-12-04 14:17   ` Andreas Ehmanns
2015-12-04 14:04 ` Gustavo Zacarias

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=20151204150354.03453463@free-electrons.com \
    --to=thomas.petazzoni@free-electrons.com \
    --cc=buildroot@busybox.net \
    /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