public inbox for openembedded-core@lists.openembedded.org
 help / color / mirror / Atom feed
From: Richard Purdie <richard.purdie@linuxfoundation.org>
To: Jonathan Liu <net147@gmail.com>
Cc: openembedded-core@lists.openembedded.org
Subject: Re: [PATCH] dbus: remove /var/run from package as it is created on startup
Date: Thu, 23 May 2013 12:38:52 +0100	[thread overview]
Message-ID: <1369309132.14887.32.camel@ted> (raw)
In-Reply-To: <1369281734-7989-1-git-send-email-net147@gmail.com>

On Thu, 2013-05-23 at 14:02 +1000, Jonathan Liu wrote:
> /var/run is a tmpfs that is created on startup.
> For sysvinit, /var/run/dbus is created by populate-volatiles.sh.
> For systemd, /var/run/dbus is created implicitly by dbus.socket when
> creating a listen stream socket at /var/run/dbus/system_bus_socket.
> 
> Signed-off-by: Jonathan Liu <net147@gmail.com>
> ---
>  meta/recipes-core/dbus/dbus.inc | 7 +++++--
>  1 file changed, 5 insertions(+), 2 deletions(-)
> 
> diff --git a/meta/recipes-core/dbus/dbus.inc b/meta/recipes-core/dbus/dbus.inc
> index 2be5bda..8055824 100644
> --- a/meta/recipes-core/dbus/dbus.inc
> +++ b/meta/recipes-core/dbus/dbus.inc
> @@ -101,9 +101,9 @@ do_install() {
>  	     > ${D}${sysconfdir}/default/volatiles/99_dbus
>  
> 
> -	mkdir -p ${D}${localstatedir}/run/dbus ${D}${localstatedir}/lib/dbus
> +	mkdir -p ${D}${localstatedir}/lib/dbus
>  
> -	chown messagebus:messagebus ${D}${localstatedir}/run/dbus ${D}${localstatedir}/lib/dbus
> +	chown messagebus:messagebus ${D}${localstatedir}/lib/dbus

Is what populate-volatiles does truly equivalent? Does this directory
need to be owned by messagebus (which is a user created by dbus) iirc?

Cheers,

Richard



  reply	other threads:[~2013-05-23 11:39 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-05-23  4:02 [PATCH] dbus: remove /var/run from package as it is created on startup Jonathan Liu
2013-05-23 11:38 ` Richard Purdie [this message]
2013-05-23 12:31   ` Jonathan Liu
2013-05-23 12:50     ` Richard Purdie

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=1369309132.14887.32.camel@ted \
    --to=richard.purdie@linuxfoundation.org \
    --cc=net147@gmail.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox