All of lore.kernel.org
 help / color / mirror / Atom feed
From: Koen Kooi <k.kooi@student.utwente.nl>
To: openembedded-devel@openembedded.org
Subject: Re: org.oe.dev dbus 1.2.1: fix pidfile location
Date: Mon, 02 Jun 2008 18:39:50 +0200	[thread overview]
Message-ID: <g217om$hae$1@ger.gmane.org> (raw)
In-Reply-To: <200806021805.03241.mickey@vanille-media.de>

Michael 'Mickey' Lauer wrote:
> On Monday 02 June 2008 17:07:10 Koen Kooi wrote:
>> Michael 'Mickey' Lauer wrote:
>>> On Saturday 31 May 2008 19:17:35 koen commit wrote:
>>>> dbus 1.2.1: fix pidfile location
>>> I'm afraid this patch breaks restartability which I fixed a couple of
>>> weeks ago. Can you double check whether you can use the init script and
>>> restart dbus still works?
>> Heh :) The fix makes this work for me:
>>
>> /etc/init.d/dbus-1 stop ; /etc/init.d/dbus-1 start
>>
>> Is that what you meant?
>
> I was using /etc/init.d/dbus-1 restart, but I think that should have the same
> semantics.

root@beagleboard:~# /etc/init.d/dbus-1 restart
Stopping Hardware abstraction layer hald
Stopping system message bus: stopped process in pidfile 
'/var/run/dbus/pid' (pid 1602)
dbus.
Starting system message bus: dbus.
Starting Hardware abstraction layer hald
root@beagleboard:~#

> Is that working for you with ash or bash?

That's with

lrwxrwxrwx  1 root root 7 May 28 17:23 /bin/sh -> busybox

regards,

Koen




      reply	other threads:[~2008-06-02 16:44 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20080531171735.3C118189300@amethyst.openembedded.net>
2008-06-02 14:49 ` [oe-commits] org.oe.dev dbus 1.2.1: fix pidfile location Michael 'Mickey' Lauer
2008-06-02 15:07   ` Koen Kooi
2008-06-02 16:05     ` Michael 'Mickey' Lauer
2008-06-02 16:39       ` Koen Kooi [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='g217om$hae$1@ger.gmane.org' \
    --to=k.kooi@student.utwente.nl \
    --cc=openembedded-devel@lists.openembedded.org \
    --cc=openembedded-devel@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.